Re: [whatwg] Fullscreen changes to support

On Tue, Apr 3, 2012 at 4:14 PM, Ian Hickson wrote: > Fullscreen then defines that when you make an element fullscreen, it's > "pushed onto the top layer", and when an element is unfullscreened, it's > "yanked from the top layer". The user "emergency escape" UI yanks all > fullscreened elements fr

Re: [whatwg] Fixing two security vulnerabilities in registerProtocolHandler

On Fri, 6 Apr 2012, Tyler Close wrote: > On Fri, Apr 6, 2012 at 3:36 PM, Ian Hickson wrote: > > On Fri, 6 Apr 2012, Tyler Close wrote: > >> > > >> > Well if it's an iframe, the parent can't be anything but the > >> > original origin, as far as I can tell. > >> > >> What happens if the handler sen

Re: [whatwg] Encoding: big5 and big5-hkscs

On 7 Apr 2012, at 15:04, Øistein E. Andersen wrote: > Suggested reverse mappings: > [...] > C6DE <= U+3003 > C6DF <= U+4EDD Sorry, these are different from the other C6xx (ETen-1) mappings. Correction: A1B2 <= U+3003 C969 <= U+4EDD Rationale: These codepoints are part of the original (unexten

Re: [whatwg] Encoding: big5 and big5-hkscs

On Fri Apr 6 14:03:22 PDT 2012, Philip Jägenstedt wrote: > So, is the > mapping I suggest, with 18594 defined mappings and 1188 U+FFFD. (Second byte 0xA1 appears as 0x7F in the mapping file.) Your table is very similar to my idea of

Re: [whatwg] Encoding: big5 and big5-hkscs

On Fri, 06 Apr 2012 23:03:22 +0200, Philip Jägenstedt wrote: So, is the mapping I suggest, with 18594 defined mappings and 1188 U+FFFD. Awesome Philip! The specification has been updated accordingly. I guess I should write some