Live data from Hacker News

HTML6 proposal for single-page apps without JavaScript

lists.w3.org

161–170 of 177 posts

Re: HTML6 proposal for single-page apps without JavaScript

#161

Single page apps seem like a hack to make browser apps feel like they are closer to native apps. Because most SPAs have a set flow, it seems like we should be able to use prefetching to tell the browser what is most likely to happen next. For example, if you are on a list, then you can tell the browser to prefetch the details. What I feel like is missing from this equation is a nice transition between pages. How nice…

I couldn't tell from your post, so just in case you weren't aware, browsers do support prefetching documents via link tags: http://www.w3.org/TR/html5/links.html#link-type-prefetch

Re: HTML6 proposal for single-page apps without JavaScript

#162

Earlier quoted context omitted.

, I don't think there's an excuse. we know for sure that it is not out of incompetence but it was probably easier to write at the time and nobody bothered to fix it because it doesn't really matter. For the , it is probably not the case here as this is just a text based site but sometimes it is easier to center an image by that tag when your site is partitioned in many margins it is not as easy to center some stuff,…

Not many but they're deprecated/obsolete for a reason, don't you think?

Perhaps not many in the design community or front end devs, but I'd wager there are plenty of developers who love
because it's what they've always used to do simple layouts so they can get back to the back end.

Re: HTML6 proposal for single-page apps without JavaScript

#163

Earlier quoted context omitted.

There's an "upvote" button, just to the left of the comment above.

You shouldn't use the upvote button for agreement. On the other hand "+1" and "I agree" and "Well said!" clutter the forum. How do we solve this?

+1 I agree.

Re: HTML6 proposal for single-page apps without JavaScript

#164

Earlier quoted context omitted.

, I don't think there's an excuse. we know for sure that it is not out of incompetence but it was probably easier to write at the time and nobody bothered to fix it because it doesn't really matter. For the , it is probably not the case here as this is just a text based site but sometimes it is easier to center an image by that tag when your site is partitioned in many margins it is not as easy to center some stuff,…

Not many but they're deprecated/obsolete for a reason, don't you think?

br is neither deprecated nor obsolete

Re: HTML6 proposal for single-page apps without JavaScript

#165
post #142
post #106

Earlier quoted context omitted.

Wrong. It was called "XMLHTTP", created by Microsoft for Outlook Web Access 2000. Mozilla implemented it as XMLHttpRequest JavaScript object in Gecko. The main reason of XHR/AJAX was XML, but Text and HTML are supported too. See Wikipedia for the correct history: http://en.wikipedia.org/wiki/XMLHttpRequest Microsoft never implemented the XHTML standards in Internet Explorer. IE cannot open files with .xhtml file exte…

Any idea what the MSDN tree view used in the 1998 timeframe? I know it loaded the contents on demand when you expand3d a node and I remember it doing so using an automation object with CreateObject.

MSDN used HTML4 frames for a long time (afaik until ca. 2006). The left side bar (left frame) with the tree was a Java applet and with the relauch in 2000 a DHTML page. The tree was expanded using DHTML (a marketing term that describes HTML with heavy Javascript usage). Javascript was used to change the visibility of DOM nodes (tree). That data of the TOC tree was loaded as XML (XMLHTTP).

Article that explains the MSDN server backend (1999): https://web.archive.org/web/19990505061257/http://msdn.micro...

Before that relaunch in 2000, the MSDN library used (MS) Java for the left side bar (TOC tree): https://web.archive.org/web/19990423231040/http://msdn.micro...

The DHTML version of MSN library (2000): https://web.archive.org/web/20000510200809/http://msdn.micro... , the 2001 version works: https://web.archive.org/web/20011108064645/http://msdn.micro...

XML toc tree data: https://web.archive.org/web/*/http://msdn.microsoft.com/libr... (sadly not archived)

Re: HTML6 proposal for single-page apps without JavaScript

#166

Earlier quoted context omitted.

em and strong would be removed in a strict HTML5 standard. All stylised elements would. Span wouldn't as span doesn't impose styling directly.

and are semantic, not stylistic.

Re: HTML6 proposal for single-page apps without JavaScript

#167
post #164

Earlier quoted context omitted.

Not many but they're deprecated/obsolete for a reason, don't you think?

br is neither deprecated nor obsolete

HECK YEE! I even put classes in my
tags so I can get at them and decide when and how they display!

Re: HTML6 proposal for single-page apps without JavaScript

#168
post #164

Earlier quoted context omitted.

Not many but they're deprecated/obsolete for a reason, don't you think?

br is neither deprecated nor obsolete

HECK YES! I even put classes in my
tags so I can get at them and decide when and how they display!

Re: HTML6 proposal for single-page apps without JavaScript

#169

Earlier quoted context omitted.

But there are millions of pages that will never be updated and if a browser can't render them people are going to blame the browser, not the use of deprecated HTML elements (an issue they won't even have awareness of).

That's just a generic argument for no new HTML ever.

No it isn't; it's an argument against breaking changes.

Re: HTML6 proposal for single-page apps without JavaScript

#170

Earlier quoted context omitted.

You shouldn't use the upvote button for agreement. On the other hand "+1" and "I agree" and "Well said!" clutter the forum. How do we solve this?

The line between "upvote for good point" and "upvote for agreement" can be blurry, same for downvoting. In either case, both are accepted uses. PG has said as much: https://news.ycombinator.com/item?id=117171

Interesting. I guess I was a bit too quick with my previous comment then.

However to me it feels a bit like discouraging alternative opinions, when they are hidden/greyed out.

Is this commonly accepted then?

Post reply on HN