On 10/3/12 11:04 PM, Boris Zbarsky wrote:
I decided it wasn't worth punishing our users further if no one else in
the world cared about this.
Oh, and for the record we added gsp support in standards mode in Firefox
14. We kept the warning when it was used until Firefox 15, somewhat by
accide
On 10/3/12 10:19 PM, Glenn Maynard wrote:
That's unfortunate. It's one of the most pathologically broken behaviors
on the platform; now there will be nothing discouraging people from using
it. I think this was a net win despite the cost to interoperability.
That is as may be, but:
1) Every
On Wed, Oct 3, 2012 at 8:44 PM, Robert O'Callahan wrote:
> Gecko *always* required getElementById in standards mode, until FF15.
> That's why most pages worked (and still do) without element IDs in the
> global scope. But no-one else was willing to follow suit, so we dropped it.
>
That's unfortun
On Wed, Oct 3, 2012 at 2:01 PM, Glenn Maynard wrote:
> On Tue, Oct 2, 2012 at 7:16 PM, Charles Pritchard wrote:
>
> > I think moz already made the move to require document.getElementById for
> > these cases.
>
> It looks like they did in FF13 (in standards mode, not quirks mode), but no
> longer
This subthread has crossed the line of what is acceptable on this mailing
list. I'd like to remind everyone that discussion on this list should
focus on technical issues and not on process discussions, and that all
communication should be respectful, and avoid presenting wild speculation
as fa
Hixie,
See below the reply from IANA about registration for application/microdata+json.
I'll make the simple "n/a" changes when I re-submit it. But see in
particular the suggestion about security.
--Mike
- Forwarded message from Amanda Baber via RT -
Subject: [IANA #598704] Registra
On 10/3/12 1:31 AM, Charles Pritchard wrote:
Mozilla has an extensive system for bug reporting.
You mean like a bug database?
I suspect their switch between various versions is related to their data as
captured by those systems.
I suspect that's bollocks, with all due respect.
They have
Hi all,
I would like to ask for your help. I'm having hard time understanding
the rules for firing WebStorage's storage event.
In section 11.2.3
(http://www.whatwg.org/specs/web-apps/current-work/multipage/webstorage.html#the-localstorage-attribute)
we have this sentence [1]:
"
When the setItem(),
On Oct 2, 2012, at 4:58 PM, Elliott Sprehn wrote:
What of the fact that this breaks existing pages with that access it as just Path? Historically this has been a
non-starter for new APIs.
On Wed, 03 Oct 2012 05:12:46 +0200, Maciej Stachowiak
wrote:
Can we get data on prevalence of such
