On Sun, 8 Jun 2008, Ojan Vafai wrote:
I can speak to the first (getNextFocusableElement). One case I have hit
where this would be useful is a designMode iframe (in this case a
rich-text editor). I wanted tab to go to the next focusable element,
which was a different element depending on
On 28/12/08 04:09, Ian Hickson wrote:
I agree that conventions differ between media, but if the author wants to
tweak the settings for each media, CSS and class values already exist to
take care of this.
That's true for authors only (the party least likely to want to tweak
settings for other
On Thu, 21 Aug 2008, Jonas Sicking wrote:
Here is the list of elements that we *don't* execute scripts inside of
in firefox:
http://mxr.mozilla.org/mozilla-central/source/content/base/src/nsScriptElement.cpp#148
i.e. iframe, noframes, noembed
Everywhere else we do execute the script.
On Sun, 28 Dec 2008, Benjamin Hawkes-Lewis wrote:
On 28/12/08 04:09, Ian Hickson wrote:
I agree that conventions differ between media, but if the author wants to
tweak the settings for each media, CSS and class values already exist to
take care of this.
That's true for authors only (the
Ian Hickson wrote on 28 december 2008 12:38:
On Thu, 12 Jun 2008, Mike Wilson wrote:
Ian Hickson wrote:
window.focus() isn't in HTML5 as there doesn't appear to
be a valid use case for it and it is too abusable, and
thus shouldn't be supported. If pages depend on it being
On , Ian Hickson i...@hixie.ch wrote:
On Fri, 12 Dec 2008, Martin Atkins wrote:
Could browsers handle confirm() and friends in such a way that they only
block the contents of the tab, not the whole browser? In particular, the
close tab and close window features, ideally along with things
On Fri, 13 Jun 2008, Adam Barth wrote:
3) The document's origin and effective script origin become the origin
and the effective script origin of the currently executing script.
(Note: actually, the origins are aliased, as in the about:blank case, so
that changes to one of the document's
Hey,
Time to send some feedback on the resolve a URL dfn.
Step 3 is (currently) If encoding is UTF-16, then change it to
UTF-8.. Does this mean we literally change just encoding to UTF-16,
and leave url verbatim, or are we meant to change url to UTF-8
too? This is currently ambiguous. Not
On Sun, Dec 28, 2008 at 6:22 PM, Adam Barth wha...@adambarth.com wrote:
On Fri, 13 Jun 2008, Adam Barth wrote:
3) The document's origin and effective script origin become the origin
and the effective script origin of the currently executing script.
(Note: actually, the origins are aliased, as
Jonas Sicking wrote:
I don't know of any websites unfortunately. I've cc'ed Boris who might know.
In general, if IE doesn't do it it seems unlikely that many sites depend on it.
Agreed on the latter.
On the former, it wouldn't be a problem for websites per se, but the
aliasing needs to
On Thu, Dec 25, 2008 at 9:51 AM, Giovanni Campagna
scampa.giova...@gmail.com wrote:
2008/12/25 Ian Hickson i...@hixie.ch
XMLHttpRequest was invented by Netscape, now it is a W3C Technical Report (I
don't remember what maturity level). The same with so called DOM level 0
(now HTML5)
No,
On Fri, 28 Nov 2008 05:01:42 +1100, Olli Pettay olli.pet...@helsinki.fi
wrote:
On 11/27/2008 06:52 PM, Calogero Alex Baldacchino wrote:
Perhaps a *good* rationale could be, if you can't see the control,
There are other modalities than just visual.
Sure. But users generally expect the page
On Sat, 15 Nov 2008 08:18:25 +1100, Ian Hickson i...@hixie.ch wrote:
On Fri, 14 Nov 2008, Filippo Levizzani wrote:
Would it be possible to have media attribute in the SCRIPT element?
Addmitted vaues would be the same of STYLE element (all, screen, print,
handheld ...)
This doesn't really
On Mon, 29 Dec 2008, Charles McCathieNevile wrote:
On Sat, 15 Nov 2008 08:18:25 +1100, Ian Hickson i...@hixie.ch wrote:
On Fri, 14 Nov 2008, Filippo Levizzani wrote:
Would it be possible to have media attribute in the SCRIPT
element? Addmitted vaues would be the same of STYLE element
14 matches
Mail list logo
