On Mon, 03 Sep 2012 15:29:13 +0200, Boris Zbarsky bzbar...@mit.edu wrote:
On 9/3/12 3:25 AM, Simon Pieters wrote:
Is there a compat problem with supporting it in quirks mode?
I did cover this in my post. The last time we tried it, there was, but
that was a while ago.
Oh, sorry.
greping
On Wed, 05 Sep 2012 21:37:58 +0200, David Young dyo...@pobox.com wrote:
On Mon, Apr 30, 2012 at 08:55:04AM +0300, Aryeh Gregor wrote:
On Sun, Apr 29, 2012 at 11:39 PM, David Young dyo...@pobox.com wrote:
I'm curious what advantages document.execCommand() has over the
customary DOM API for
On Wed, 05 Sep 2012 22:47:07 +0200, Ian Hickson i...@hixie.ch wrote:
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1736
Webkit returns undefined, whereas IE, Gecko, and Opera all return an
HTMLCollection. (IE returns an HTMLCollection with a tags() method, Gecko
and Opera do
On Sat, Sep 1, 2012 at 4:22 AM, David Young dyo...@pobox.com wrote:
This demonstrates some unexpected contenteditable results on
Chrome 21.0.1180.82 under Mac OS X. I cannot seem to return the
contenteditable to the empty state again---i.e., to the state where the
placeholder shows---using
On Wed, Sep 5, 2012 at 10:37 PM, David Young dyo...@pobox.com wrote:
I have to say that I'm uneasy with the way that this API wavers between
answering interaction-design questions and telling what ought to happen
to the DOM under, say, an execCommand('insertText'). Just for example,
lots of
On Wed, 05 Sep 2012 19:45:41 +0200, Mathew Marquis m...@matmarquis.com
wrote:
I can say for my own part: manipulating strings is far more difficult
than manipulating the value of individual attributes. It’s hard to
imagine a situation where I’d prefer to muck through a space/comma
On Thu, Sep 6, 2012 at 3:56 AM, Aryeh Gregor a...@aryeh.name wrote:
It should never be possible to make a contenteditable element contain
nothing, once it has something in it, because then it would collapse
to zero height and you wouldn't be able to click on it. (IIRC, some
browsers have
On Wed, Sep 5, 2012 at 1:47 PM, Ian Hickson i...@hixie.ch wrote:
For HTMLOptionsElement, the situation is more murky.
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1739
From what I can tell, IE doesn't do direct named access, you have to do it
via item() or namedItem(). The
Hi there,
I developed a javascript table parser based on my research. The parser is
able to understand complex relationship in a data table. The relationship
association is based on the current algorithm and take in consideration how
the header cell (th) is structured, positioned and spanned. All
On Thu, Sep 6, 2012 at 3:56 AM, Aryeh Gregor a...@aryeh.name wrote:
On Sat, Sep 1, 2012 at 4:22 AM, David Young dyo...@pobox.com wrote:
This demonstrates some unexpected contenteditable results on
Chrome 21.0.1180.82 under Mac OS X. I cannot seem to return the
contenteditable to the empty
On Mon, 16 Jul 2012, Robert Eisele wrote:
Browsers are very restrictive when one tries to access the contents of
different domains (including the scheme), embedded via framesets. This
is normally a good practice, but I'd suggest to weaken this restriction
for the data: URI schema.
It
On Wed, 18 Jul 2012, Anne van Kesteren wrote:
I think we should expand http://html5.org/r/7180 with a mention of
XMLHttpRequest's open() method. XMLHttpRequest already has a section
detailing how data URLs behave in an HTTP context, but they are not yet
explicitly allowed. Allowing them in
help
2012/9/6 whatwg-requ...@lists.whatwg.org
Send whatwg mailing list submissions to
whatwg@lists.whatwg.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.whatwg.org/listinfo.cgi/whatwg-whatwg.org
or, via email, send a message with subject or body
On Fri, 27 Jul 2012, Leif Halvard Silli wrote:
I have just written a document on how implementations prioritize
encoding info for HTML documents.[1] (As that document shows, I have not
tested Safari 6.) Based on my findings there, I would like to suggest
that the spec's encoding sniffing
I'm currently building an analysis system like Google Analytics, which
gets embedded into a website via a small JavaScript snippet. When I
analyzed the data, I came across a very interesting trick because I got
a lot of requests (with the data from location.href) where the entire
This email is an extension of the thread started at
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2012-August/036953.html
by John Mellor, distilling the core problem he has into a more
easily-understood and digested form.
The srcset attribute, as currently written, is not friendly to large
From: jackalm...@gmail.com
...
I'm not sure how best to solve this, but John Mellor suggested
allowing the specification of the image's native dimensions somehow.
That way, the browser could know that the 1600.jpg image is
appropriate to serve as an 800px wide high-dpi image, or a 1600px
On Mon, 6 Aug 2012, Ian Melven wrote:
the spec at
http://www.whatwg.org/specs/web-apps/current-work/multipage/origin-0.html#sandboxed-origin-browsing-context-flag
says :
This flag also prevents script from reading from or writing to the
document.cookie IDL attribute, and blocks
On Mon, 6 Aug 2012, Ian Melven wrote:
Adom wrote:
Yes. I think this is actually a consequence of having a unique origin
and doesn't need to be stated explicitly in the spec. (Although we
might want to state it explicitly for the avoidance of doubt.)
yeah, i can see how this situation
On Fri, 10 Aug 2012, Erik Reppen wrote:
My understanding of the general philosophy of HTML5 on the matter of
malformed HTML is that it's better to define specific rules concerning
breakage rather than overly strict rules about how to do it right in the
first place
This is incorrect. The
On Mon, 27 Aug 2012, Tab Atkins Jr. wrote:
On Mon, Aug 27, 2012 at 10:56 AM, Ian Hickson i...@hixie.ch wrote:
On Wed, 3 Aug 2011, Tab Atkins Jr. wrote:
On Wed, Aug 3, 2011 at 8:50 AM, Randy ra...@prowebdesign.nl wrote:
On top of that, the vast majority of these readers just translate
On Fri, 7 Sep 2012, Fred Andrews wrote:
I think the aim is to have the URL of the page that includes these data:
URLs sent to the tracking server?
Ah, I see. So say you have a page A, which itself contains a data: URL,
and you load that data: URL as page B, and in B there is a link to
Ian Hickson i...@hixie.ch, 2012-09-07 04:25 +:
On Fri, 10 Aug 2012, Erik Reppen wrote:
Why can't we set stricter rules that cause rendering to cease or at least a
non-interpreter-halting error to be thrown by browsers when the HTML is
broken from a nesting/XML-strict-tag-closing
On Wed, 22 Aug 2012, Jukka K. Korpela wrote:
2012-08-22 3:43, Ian Hickson wrote:
[...] the argument is that WYSIWYG editor implementors will be
pressured into making their tools output conforming content by people
who don't understand the subtlties of this thread, based purely on
24 matches
Mail list logo
