On Sat, 28 Aug 2010 03:16:16 +0200, Ojan Vafai o...@chromium.org wrote:
WebKit has added the input event to contentEditable nodes. That part of
this proposal seemed non-controversial. Do other browser vendors support
changing the description of this event to apply to contentEditable nodes
I saw HTML5 spec 's
introductionhttp://www.whatwg.org/specs/web-apps/current-work/multipage/introduction.html#introductionincludes
the following content,
Features that are not currently in this document that were in the past
considered part of HTML5...,, include:... Web Storage
I know Web Storage
Many features are now in separate specifications / drafts, linked to in the
introduction you reference. It doesn't mean they're dead, indeed web storage
has been implemented by a number of browsers as have other features listed
there such as geolocation, websockets, etc. Don't read too much into
According to HTML5 spec, the embed tag can play a swf file, however, the
object tag can also play a swf file (though object is defined in HTML4).
I don't understand why need the embed tag , because the object tag can
support(or embed) many objects such as images, audio, videos, Java applets,
On Sat, Aug 28, 2010 at 8:16 AM, zhao Matt mattzhao...@gmail.com wrote:
According to HTML5 spec, the embed tag can play a swf file, however, the
object tag can also play a swf file (though object is defined in HTML4).
I don't understand why need the embed tag , because the object tag can
On Fri, Aug 27, 2010 at 9:54 PM, E.J. Zufelt li...@zufelt.ca wrote:
Good evening,
I am rather new to this list and am curious if anytime recently there has
been discussion about adding tabstrip and tab elements to the html5 spec?
The concept of a tabstrip is a rather commonly used UI
On 28 Aug 2010, at 06:10, E.J. Zufelt wrote:
1. nav is for navigation, but in a web app selecting a tab may nave nothing
to do with navigation, it may have to do with switching UI pages, which
could potentially be considered navigation.
I can't grok this sentence. You say it may have nothing
On 2010-08-28, at 6:25 PM, Benjamin Hawkes-Lewis wrote:
On 28 Aug 2010, at 06:10, E.J. Zufelt wrote:
1. nav is for navigation, but in a web app selecting a tab may nave nothing
to do with navigation, it may have to do with switching UI pages, which
could potentially be considered
On Sat, Aug 28, 2010 at 3:32 PM, E.J. Zufelt li...@zufelt.ca wrote:
It is important to provide semantic markup for complex UI controls where they
are common, tabstrip/tab is one example of a common UI component that
requires markup. This way meaningful information about the role of the
On 2010-08-28, at 6:40 PM, Tab Atkins Jr. wrote:
On Sat, Aug 28, 2010 at 3:32 PM, E.J. Zufelt li...@zufelt.ca wrote:
It is important to provide semantic markup for complex UI controls where
they are common, tabstrip/tab is one example of a common UI component that
requires markup. This way
On 28 Aug 2010, at 23:39, E.J. Zufelt wrote:
I am suggesting that a different tab page would not be navigation in the
common sense, as the user is not leaving the current page, just switching
contexts within the application.
But the draft is explicit that links in a nav element might only
Hello all,
I wanted to chime in on this discussion. Let me say up front that clearly the
w3c and the browser vendors all are on the same page as you, Ian. I'm not in
the position to be challenging your collective wisdom!
But, I share some of the same concerns (and more) as David Bruant, and
What percentage of all versions of all browsers do you think fully
support any version of any spec? Saying that browser X supports some
part of CSS2 is no more or less useful than saying browser X supports
some part of CSS as it is defined today (which is backward compatible
with how it was
I would guess that new features would go in their own spec, like Web
Workers, WebSockets, and so on. If that is the case, you can still say
browser X supports things by naming the specs, e.g. Chrome supports
WebSockets.
~Jonathan Castello
On Sat, Aug 28, 2010 at 8:15 PM, David John Burrowes
14 matches
Mail list logo
