Re: [whatwg] WhatWG and

2006-09-01 Thread Shadow2531
On 9/1/06, Christian Biesinger <[EMAIL PROTECTED]> wrote: Shadow2531 wrote: > Yes, it's arguably a bug, but I do like this bug because I can use > only one object element to do IE's classid way and the normal way. > It's a compatibility feature imo. However, I can't use it in > production withou

Re: [whatwg] WhatWG and

2006-09-01 Thread Christian Biesinger
Sorry for replying to this a bit late, but other stuff kept me distracted the last two weeks... I should maybe also note that the purpose of the question wasn't so much to introduce new attributes to embed with (maybe) nicer semantics, but more about how to implement as it exists today in a w

[whatwg] Server-sent events or Server-sent DOM events?

2006-09-01 Thread akusaya
Since Opera made a demo of the above technology, I want to publicize it more. But I'm confused as what term is more suitable. There are two mention of this technology in http://whatwg.org/specs/web-apps/current-work/ In Abstract section, "This specification introduces features to HTML and the DOM

Re: [whatwg] Scoped tabindex proposal

2006-09-01 Thread Brad Fults
On 9/1/06, Aaron Leventhal <[EMAIL PROTECTED]> wrote: Don't try to overload the tabindex attribute. First, the browsers currently optimize it knowing that it's an integer. Second, the scoping is orthogonal. Third, magic values are less readable. It's voodoo. Yes, yes, and yes. Completely agreed

Re: [whatwg] Scoped tabindex proposal

2006-09-01 Thread Aaron Leventhal
tabindex="-1" doesn't just remove items from the tab order. It also makes items focusable via mouse click or script, which is important when designing custom container widgets like spreadsheets, etc. via Javascript. In fact any negative value does it. Don't try to overload the tabindex attribu

Re: [whatwg] Scoped tabindex proposal

2006-09-01 Thread Simon Pieters
Hi, From: Ric Hardacre <[EMAIL PROTECTED]> how about allowing decimals, where by default "1" implies "1.0"? : [...] This also allows you to quickly associate the grouping of an input by it's value when viewing the source: You can already do that; just use tabindex 11, 21, 12, 22 and 30. Reg

Re: [whatwg] Scoped tabindex proposal

2006-09-01 Thread Ric Hardacre
Andrew Fedoniouk wrote: > > It is better to use another attribute for that, say - tabgroup. > It should accept exactly the same set of values as tabindex. > > > > > > > > > The order of tab traversal of inputs will be in this case as > their natural order (in this case). > > tabgr