Re: [WebIDL] T[] migration

On Thu, 07 Jan 2016 20:12:44 +0100, Boris Zbarsky wrote: On 12/18/15 3:53 AM, Simon Pieters wrote: Note that it requires liveness. Does that work for a frozen array? No. You'd have to create a new array object at the point when you want to update the set of values in the array.

Re: Can we land heycam's WebIDL tests as-is and address review comments following?

71 git push -u origin webidl-tests -- Simon Pieters Opera Software

Re: [WebIDL] T[] migration

On Fri, 18 Dec 2015 18:04:27 +0100, Olli Pettay wrote: On 12/18/2015 06:20 PM, Domenic Denicola wrote: From: Simon Pieters [mailto:sim...@opera.com] Note that it requires liveness. Does that work for a frozen array? Frozen array instances are frozen and cannot change. However, you can

Re: [WebIDL] T[] migration

;> would be possible, of course. Fixed in https://github.com/w3c/csswg-drafts/commit/e8a91deb46b670d6c2d8d302492a64222928d08a Note that it requires liveness. Does that work for a frozen array? Maybe this particular API should be a method instead that returns a sequence? -- Simon Pi

Re: [websockets] Test results available

org/websockets/keeping-connection-open/001.html which is all-"Timeout". This test passes for me in Blink and Gecko. It has a indicating it needs a long timeout. Is it a bug in the test runner being used here? -- Simon Pieters Opera Software

Re: [websockets] Test results available

On Thu, 26 Mar 2015 16:37:28 +0100, Olli Pettay wrote: websockets/interfaces.html the test itself has bugs (uses old idlharness.js?). https://github.com/w3c/web-platform-tests/pull/1714 -- Simon Pieters Opera Software

Re: [websockets] Test results available

Spec now says [TreatNonObjectAsNull] so this should return the object, not null. https://html.spec.whatwg.org/multipage/webappapis.html#eventhandlernonnull Fix: https://github.com/w3c/web-platform-tests/pull/1704 -- Simon Pieters Opera Software

Re: [websockets] Test results available

On Thu, 02 Apr 2015 14:15:10 +0200, Simon Pieters wrote: http://www.w3c-test.org/websockets/interfaces/WebSocket/readyState/003.html looks wrong to me: the value it should get is in fact undefined, since the property got deleted from the prototype. (Will have a look.) http

Re: [websockets] Test results available

On Thu, 02 Apr 2015 14:15:10 +0200, Simon Pieters wrote: http://www.w3c-test.org/websockets/keeping-connection-open/001.html -- the test is wrong. Passing undefined means the argument is not present per Web IDL, so this should not throw. I assume you mean some other test since that test

Re: [websockets] Test results available

ill have a look.) -- Simon Pieters Opera Software

Re: CfC: publish Proposed Recommendation of Web Messaging; deadline March 28

/webmessaging/all.html> [<2] <http://w3c.github.io/test-results/webmessaging/less-than-2.html> [PR] <http://www.w3.org/TR/2015/PR-webmessaging-20150407/> [CR] <http://www.w3.org/TR/2012/CR-webmessaging-20120501/> [PC] <http://dev.w3.org/html5/postmsg/#broadcasting-to-many-ports&g

Re: [XHR] UTF-16 - do content sniffing or not?

On Mon, 23 Mar 2015 14:32:27 +0100, Hallvord Reiar Michaelsen Steen wrote: On Mon, Mar 23, 2015 at 1:45 PM, Simon Pieters wrote: On Sun, 22 Mar 2015 23:13:20 +0100, Hallvord Reiar Michaelsen Steen < hst...@mozilla.com> wrote: Given a server which sends UTF-16 data with a UTF-16 B

Re: [XHR] UTF-16 - do content sniffing or not?

utf-16 BOM) and JSON response (always decodes as utf-8). -- Simon Pieters Opera Software

Re: oldNode.replaceWith(...collection) edge case

you have the need to pass the context node as an argument along with other nodes, just use before() and after() to insert these other nodes? And even insert them one by one is fine? Yeah. -- Simon Pieters Opera Software

Re: oldNode.replaceWith(...collection) edge case

optimal. In all cases it would be just one reflow after the script has finished, unless you force a reflow by asking for layout information (e.g. offsetTop) between the mutations. -- Simon Pieters Opera Software

Re: Defining a constructor for Element and friends

a more specific interface. How do you envision to solve this? Should we assign element-specific interfaces to all post-HTML4 elements now, just in case? Or make new HTMLElement('ruby') create an HTMLRubyElement? Something else? -- Simon Pieters Opera Software

Re: [editing] Responsive Input Terminology

On Fri, 12 Dec 2014 17:02:25 +0100, Frederico Knabben wrote: On Friday, 12 December 2014 at 14:40, Simon Pieters wrote: How about "device-independent events"? Aren’t we missing what kinds of events we’re talking about? We would just know that those events are device-independent

Re: [editing] Responsive Input Terminology

s the model. If not, would "abstract events" or simply "high-level events" work? Sorry if these have already been discussed and dismissed (haven't had much time to look through the archives, tbh). How about "device-independent events"? -- Simon Pieters Opera Software

Re: [eventsource] ACTION-742: Re sse test results, followup on the timeouts with the 2 test facilitators (Web Applications Working Group)

x27;s global object is either a Window object or an object implementing the WorkerUtils interface. ]] Thoughts, Simon & Odin? Redundant with [Exposed]. Please use https://html.spec.whatwg.org/multipage/comms.html#server-sent-events when implementing. What Anne said. :-) -- Simo

Re: [Custom] Custom elements and ARIA

though, the default implicit ARIA semantics are still UA requirements, right? Yes. [...] -- Simon Pieters Opera Software

Re: HTML imports: new XSS hole?

On Mon, 02 Jun 2014 11:32:45 +0200, Anne van Kesteren wrote: How big of a problem is it that we're making as dangerous as

Re: where do tests for window.opener go?

still annotate some of them as being a test for another section, you can do that with . -- Simon Pieters Opera Software

Re: Custom Elements: 'data-' attributes

research if it's safe to add a new global attribute, it's not enough to measure how often such an attribute is used in the wild. We need to research bare names in event handlers also. -- Simon Pieters Opera Software

Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?

On Wed, 18 Dec 2013 11:58:07 +0100, Simon Pieters wrote: On Tue, 17 Dec 2013 17:06:57 +0100, Boris Zbarsky wrote: On 12/17/13 3:29 AM, Jonas Sicking wrote: This is a good point. Would this have performance implications for down-level browsers? I don't know if prescanners e

Re: inline declarative manifest, was Re: New manifest spec - ready for FPWD?

On Tue, 17 Dec 2013 17:06:57 +0100, Boris Zbarsky wrote: On 12/17/13 3:29 AM, Jonas Sicking wrote: This is a good point. Would this have performance implications for down-level browsers? I don't know if prescanners etc in contemporary browsers are smart enough to ignore

Re: Refactoring SharedWorkers out of Web Workers W3C spec

Workers> [Tests] <http://w3c-test.org/web-platform-tests/master/workers/> [Mins] <http://www.w3.org/2013/11/12-webapps-minutes.html#item08> -- Simon Pieters Opera Software

Re: Refactoring SharedWorkers out of Web Workers W3C spec

ve. However I'd really like to see us start a level 2 of the spec. The synchronous messaging channels is something else I'd like to see done there. / Jonas -- Simon Pieters Opera Software

Re: Refactoring SharedWorkers out of Web Workers W3C spec

motivation here. I'd rather we remove the first exit criteria than try to punch conformance holes in the spec for failing tests. -- Simon Pieters Opera Software

Re: Sync IO APIs in Shared Workers

On Fri, 22 Nov 2013 03:33:51 +0100, Jonas Sicking wrote: The only browser shipping SharedWorkers is Chrome (not sure if Opera does too?), Yes, both Presto-based (since Opera 10.60) and Chromium-based. -- Simon Pieters Opera Software

Re: Define window.orientation

On Wed, 06 Nov 2013 01:17:31 +0100, Jonas Sicking wrote: window.screen.orientation seems like a better way forward. Why would window.screen.orientation be any more correctly implemented than window.orientation? -- Simon Pieters Opera Software

Re: [webcomponents]: Allowing text children of ShadowRoot is a bad time

On Tue, 29 Oct 2013 00:54:05 +0100, Anne van Kesteren wrote: We are considering not throwing in XML. Only on getting innerHTML, though, right? -- Simon Pieters Opera Software

Re: [clipboard] typo in WebIDL

On Tue, 08 Oct 2013 17:19:51 +0200, Boris Zbarsky wrote: On 10/8/13 7:47 AM, Simon Pieters wrote: Pro tip: use http://www.w3.org/2009/07/webidl-check (I invoke it in my Makefile for CSSOM). Hmm. What makes sure this is updated when the spec is updated? I just tried this: interface

Re: [clipboard] typo in WebIDL

. Guilty, and fixed - I obviously need to study that WebIDL spec in some detail.. :-/ Pro tip: use http://www.w3.org/2009/07/webidl-check (I invoke it in my Makefile for CSSOM). -- Simon Pieters Opera Software

Re: when will serializing a document throw?

pletely empty document..? :-) XML can't represent an empty document. -- Simon Pieters Opera Software

Re: when will serializing a document throw?

d? Or should we just drop that test and leave that spec statement untested? Why would you drop the test? -- Simon Pieters Opera Software

Re: [XHR] statusText, status and network errors

te-the-request -> "Set the error flag." http://xhr.spec.whatwg.org/#dom-xmlhttprequest-statustext -> "If the error flag is set, return the empty string." (I'm not sure where the spec says that the above case is a network error, though.) -- Simon Pieters Opera Software

Re: [XHR] responseXML.referrer

. Where is / should this be spec'ed? http://www.whatwg.org/specs/web-apps/current-work/multipage/dom.html#dom-document-referrer The XHR spec doesn't seem to set "the document's referrer", so the value is the empty string per spec. -- Simon Pieters Opera Software

Re: [XHR] xhr.responseXML.cookie ?

thing, per spec. -- Simon Pieters Opera Software

Re: [XHR] Content-Length header for data: URLs

would hardly call taking the length subtracting any characters before the "," and applying a multiplier "parsing". You don't have to look at any characters after the "," at all. Just applying a multiplying doesn't take percent-escaping into account, though. -- Simon Pieters Opera Software

Re: [webcomponents]: Shadow DOM + CSS = <3 Meeting Summary

rstand how this idiom is supposed to work when you have a list of selectors as argument. Consider: video::cue(b, i) { background:lime } If it's changed to video::cue b, i { background:lime } then that looks like there are two selectors, "video::cue b" and "i". -- Simon Pieters Opera Software

Re: Kickoff application manifest work

. Anything else seems like a potential for new security problems. -- Simon Pieters Opera Software

Re: [screen-orient] why not provide at CSSOM API to CSS Device Adaptation instead?

rfaces Is that sufficient? -- Simon Pieters Opera Software

Re: webcomponents: instead of

On Wed, 15 May 2013 20:26:36 +0200, Dimitri Glazkov wrote: On Tue, May 14, 2013 at 2:21 PM, Simon Pieters wrote: That seems to be an argument based on aesthetics. That's worth considering, of course, but I think is a relatively weak argument. In particular I care about the

Re: webcomponents: instead of

On Tue, 14 May 2013 09:45:01 +0200, Hajime Morrita wrote: Just after started prototyping HTML Imports on Blink, this idea comes to my mind: Why not have for HTML Imports? The good old has its own semantics which allows users to change the attributes dynamically. For example, you can c

Re: Fixing appcache: a proposal to get us started

EDIA block per resource? This doesn't include the media="" attribute of , but I think that should be dropped from the element anyway. Something similar could be done for , maybe, which is a different beast than . It's a bit verbose, but it's a lot less verbose than loading the content twice. -- Simon Pieters Opera Software

Re: Monkeypatching document.createElement() is wrong

("img") are equivalent and no additional magic is required. Same for new Audio() and createElement("audio"). Not quite, actually. new Audio() sets the content attribute preload="auto". -- Simon Pieters Opera Software

Re: [editing] defaultParagraphSeparator

ec). * Argument is case insensitive * The only available options are "P" and "DIV" * Default is "P" In Presto, yes. Is that correct? Thanks Alex -- Simon Pieters Opera Software

Re: [editing] defaultParagraphSeparator

div'? Only p and div addresses the use case of p having undesirable style. If there is a chance to settle on what's right for any of these, it would be awesome. Alex [1] https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html#the-defaultparagraphseparator-command -- Simon Pieters Opera Software

Re: RfR: Web Workers Test Cases; deadline March 28

ep of the first test. http://w3c-test.org/webapps/Workers/tests/submissions/Microsoft/postMessage_ports_readonly_array.htm The bulk of the code should be in a step() since if e.g. `new MessageChannel()` throws, the harness doesn't catch it. This probably applies to most tests. The postMessage tests appear to be testing MessageChannel rather than workers. -- Simon Pieters Opera Software

Re: [PointerLock] Should there be onpointerlockchange/onpointerlockerror properties defined in the spec

that. -- Simon Pieters Opera Software

Re: Review of the spec

-weight and introducing several documents into the mix means that we have to deal with issues like making sure that those documents have the same behavior (for example, if HTML elements in those documents uppercase the nodeName or not) / Jonas -- Simon Pieters Opera Software

Re: [webcomponents] More backward-compatible templates

: 1em; margin-bottom: 1em; font-family: monospace; white-space: pre; unicode-bidi: isolate; -- Simon Pieters Opera Software

Re: Scrolling when document.documentElement requests fullscreen

/* etc... */ } Before I make this change in Gecko I'd like to get consensus from other implementers that we want this behaviour, and get the spec changed to reflect that. Sounds good to me. Regards, Chris Pearce. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=779286#c18 -- Simon Pieters Opera Software

Re: [FileAPI] File.slice spec bug

() spec without prefix. https://bugzilla.mozilla.org/show_bug.cgi?id=725289 https://bugs.webkit.org/show_bug.cgi?id=78111 -- Simon Pieters Opera Software

Re: [selectors-api] Consider backporting find() behavior to querySelector()

On Mon, 18 Jun 2012 16:57:17 +0200, Kang-Hao (Kenny) Lu wrote: (12/06/18 22:45), Simon Pieters wrote: I think we should instead either fix the old API (if it turns out to not Break the Web) or live with past mistake (if it turns out it does). To find out whether it Breaks the Web (and the

[selectors-api] Consider backporting find() behavior to querySelector()

tible change to querySelector() in nightly/aurora (or equivalent) in one or more browsers for some time. -- Simon Pieters Opera Software

Re: [selectors-api] NAMESPACE_ERR or SYNTAX_ERR when both applied

but I'd note that in the corner case These are valid: |a *|a My proposed spec change: # If the group of selectors include namespace prefixes that need to # be resolved, the implementation must raise a NAMESPACE_ERR # exception. s/NAMESPACE_ERR/SYNTAX_ERR/ -- Simon Pieters Opera Software

Re: Proposal: add websocket close codes for "server not found" and/or "too many websockets open"

suggest for 1006 ("connection could not be opened" or something like that) added somewhere (again I assume RFC 6455 isn't possible, but the IANA database and/or the W3C spec). As above. best, Jason Mozilla -- Simon Pieters Opera Software

Re: CfC: publish FPWD of Fullscreen spec; deadline May 24

set another property for replaced elements. content-fit or some such. Do you mean object-fit? I guess it would be nice for images to be object-fit:contain in fullscreen. (Videos already are.) -- Simon Pieters Opera Software

Re: Proposal: Document.parse() [AKA: Implied Context Parsing]

On Fri, 25 May 2012 09:01:43 +0200, Rafael Weinstein wrote: Ok, so from consensus on earlier threads, here's the full API & semantics. Now's the time to raise objections to UA's adding support for this feature. - 1) The Document interface is extended to include a new method: Docu

Re: Proposal: add websocket close codes for "server not found" and/or "too many websockets open"

On Wed, 23 May 2012 06:21:21 +0200, Jason Duell wrote: On Mon, 21 May 2012 12:28:16 +0200, Simon Pieters wrote: 4. If the connection could not be opened, either because a direct connection failed or because any proxy used returned an error, then the client MUST _Fail the

Re: Proposal: add websocket close codes for "server not found" and/or "too many websockets open"

On Mon, 21 May 2012 12:28:16 +0200, Simon Pieters wrote: On Wed, 16 May 2012 02:17:45 +0200, Jason Duell wrote: So the Web Socket spec is a little vague on how JS is notified when the targeted web socket server is down/nonexistent/etc. Firefox is firing an 'error' event when th

Re: Proposal: add websocket close codes for "server not found" and/or "too many websockets open"

close code for this is. Ideas? Perhaps we could also use a dedicated code for this case too. Or throw an exception? Or queue the connection? I've touched on this subject before, but we didn't reach any conclusion as to what the right thing to do is. Jason Duell Mozilla -- Simon Pieters Opera Software

Re: [webcomponents] Use x:: instead of x-?

te instead. This violates the DOM Consistency design principle. The colon in element and attribute names is trouble. We should try hard to avoid it. -- Simon Pieters Opera Software

Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML

On Wed, 09 May 2012 22:32:08 +0200, Scott González wrote: Perhaps I'm missing something, but isn't "foobar" an invalid use case? Any top-level element that needs a context can't be mixed with a text node. Are there cases where this isn't true? "f

Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML

On Wed, 09 May 2012 19:29:42 +0200, Ryosuke Niwa wrote: On May 9, 2012 10:26 AM, "Simon Pieters" wrote: On Wed, 09 May 2012 19:01:42 +0200, Ian Hickson wrote: Quick alternative proposal that might work for both parsing and DocumentFragment.innerHTML: Have createDocume

Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML

set up to act like the element for the purposes of being popped off. (Except when parsing without a browsing context, then you just parse normally.) Not sure how solid this is, but it's an idea at least. Hopefully an original one, though I'm sure y'all have considered it before. :-) -- Simon Pieters Opera Software

Re: [IndexedDB] Checked in fix for ReSpec issue

ay from depending on the current style. Yes, I would much prefer if specs currently using ReSpec moved towards using algorithms like the HTML spec. It's much clearer and is less likely to have gaping holes for edge cases. -- Simon Pieters Opera Software

Re: [webcomponents] Template element parser changes => Proposal for adding DocumentFragment.innerHTML

at innerHTML on non-HTML elements currently always parses in the "in body" insertion mode. I'd like to see that fixed before we try to support foreign content in contextless innerHTML. https://www.w3.org/Bugs/Public/show_bug.cgi?id=16635 Any other tagName => HTMLBodyElement -- Simon Pieters Opera Software

Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer

XMLHttpRequest? Is there existing content depending on BlobBuilder and its ArrayBufferView stuff? I thought the idea was to not have BlobBuilder at all. -- Anne van Kesteren http://annevankesteren.nl/ -- Simon Pieters Opera Software

Re: Shared workers - use .source instead of .ports[0] ?

t all. It might continue to work if we decide that it's needed for back compat, but it seems like we eventually would be able to get rid of it given how new the property still is. / Jonas -- Simon Pieters Opera Software

Re: Shared workers - use .source instead of .ports[0] ?

posed. Are there any particular parts you are worried about? I proposed setting ports to null. -- Simon Pieters Opera Software

Re: Shared workers - use .source instead of .ports[0] ?

[newPort]. In the new world where postMessage() supports a transfer object, I think the appropriate analogous connect event would be to result in a MessageEvent with both the |data| and |ports| attributes pointing at an array containing a single MessagePort. I don't think putting the MessagePort as the source attribute is the right model. I don't think authors think of it in this way. -- Simon Pieters Opera Software

Re: Shared workers - use .source instead of .ports[0] ?

o swap the "WindowProxy" type of .source to "any" just for this case. Anne said the type could be (WindowProxy or MessagePort)?. I am curious to see where this latest discussion on perhaps using a different Event interface for "connect" events will lead... -- Simon Pieters Opera Software

Re: Shared workers - use .source instead of .ports[0] ?

On Tue, 10 Apr 2012 14:01:47 +0200, Jarred Nicholls wrote: On Tue, Apr 10, 2012 at 1:20 AM, Simon Pieters wrote: On Wed, 04 Apr 2012 18:37:46 +0200, Jonas Sicking wrote: Sounds great to me. The ports attribute is basically useless except in this one instance since ports are these days

Re: Shared workers - use .source instead of .ports[0] ?

win to me. I'd like to have an opinion from WebKit and Microsoft about this proposal. Can someone comment or cc relevant people, please? cheers / Jonas On Wednesday, April 4, 2012, Simon Pieters wrote: Hi, In Opera Extensions we use something that resembles shared workers

Shared workers - use .source instead of .ports[0] ?

hared Workers as well. I think shared workers hasn't seen wide adoption yet, so maybe changes like this are still possible. What do people think? currently: onconnect = function(e) { e.ports[0].postMessage('pong') } proposed change: onconnect = function(e) { e.source.p

Re: [XHR] Constructor behavior seems to be underdefined

On Mon, 02 Apr 2012 07:50:21 +0200, Boris Zbarsky wrote: On 4/2/12 1:33 AM, Simon Pieters wrote: Yes, but what do they use for the origin of the Worker object itself? "Run a worker for the resulting absolute URL, with the script's browsing context of the script that invoked the

Re: [XHR] Constructor behavior seems to be underdefined

On Mon, 02 Apr 2012 07:20:27 +0200, Boris Zbarsky wrote: On 4/2/12 12:58 AM, Simon Pieters wrote: I believe some things in the HTML spec uses the entry script, at least for the purpose of choosing origin or base URL. For instance: WebSocket, Worker. Yes, but what do they use for the origin

Re: [XHR] Constructor behavior seems to be underdefined

reate platform objects associated with a different global than the constructor itself? I believe some things in the HTML spec uses the entry script, at least for the purpose of choosing origin or base URL. For instance: WebSocket, Worker. -- Simon Pieters Opera Software

Re: WebSockets -- only TCP?

HTML5 environment with deprecated support for these technologies such options would have no standing ground. See PeerConnection in http://dev.w3.org/2011/webrtc/editor/webrtc.html I hope this is helpful feedback. Best wishes, Rick van Rein OpenFortress -- Simon Pieters Opera Software

Re: [FileAPI, common] UTF-16 to UTF-8 conversion

data. Why is this better than throwing an exception? -- Simon Pieters Opera Software

Re: [FileAPI, common] UTF-16 to UTF-8 conversion

PIs. If the only way to get them is a JS escape, then an exception seems OK. I think WebSocket should do the same, for the same reason. Have you filed a bug? -- Simon Pieters Opera Software

Re: [IndexedDB] Numeric constants vs enumerated strings

hink if we want the end result to be strings only, the best way to get there is for everyone to remove support for constants and numbers at the same time as they implement support for strings. -- Simon Pieters Opera Software

Re: Selection of a document that doesn't have a window

quot; So should the spec follow IE? If not, what definition should we use to determine which documents get selections? -- Simon Pieters Opera Software

Re: Pressing Enter in contenteditable: or or ?

On Wed, 11 Jan 2012 16:39:48 +0100, Aryeh Gregor wrote: On Tue, Jan 10, 2012 at 3:50 PM, Ryosuke Niwa wrote: p has default margins. That alone is enough for us not to adopt p as the default paragraph separator. On Wed, Jan 11, 2012 at 5:15 AM, Simon Pieters wrote: Sure, but some apps like

Re: Pressing Enter in contenteditable: or or ?

emain different across applications, It already is different across applications, because they implement the default paragraph separator setting themselves. which is confusing for many users. It might be less a hassle to have maintainers of existing applications insert a line of code that triggers legacy behavior, if this is crucial for their application. -- Simon Pieters Opera Software

Re: Pressing Enter in contenteditable: or or ?

iant behavior. That would rather miss the point of having the spec IMHO. If we all implement a global switch to opt in to a different behavior, let's design a new, sane editing API instead. But I think the editing spec should try to reach interop for the legacy feature first. - Ryosuke

Re: Pressing Enter in contenteditable: or or ?

he spec, this is still a rough draft and I haven't tried to pin corner cases down yet, so it's probably not advisable to try implementing it yet as written. As always, you can see how the spec implementation behaves for various input by looking at autoimplementation.html: http://aryeh.name/spec/editcommands/autoimplementation.html#insertparagraph -- Simon Pieters Opera Software

Re: Barewords in on* attributes, redux (also, find() and company)

On Wed, 14 Dec 2011 09:15:12 +0100, Boris Zbarsky wrote: On 12/14/11 3:01 AM, Simon Pieters wrote: What I have so far as a result is a list of about 1.7 million barewords used across several tens of thousands of pages. Do you have a more accurate figure for the number of pages? "5

Re: Barewords in on* attributes, redux (also, find() and company)

).children, searchString.value)" 2) http://bookmark.people.com.cn/index.html has onclick="find()" These would both obviously get broken by the proposed find() API, unless we actually do some sort of workaround for this problem... -Boris -- Simon Pieters Opera Software

Re: [FileAPI] createObjectURL isReusable proposal

we're hoping this will be adopted in the File API spec. Thanks, Adrian. [1] http://www.w3.org/2011/11/01-webapps-minutes.html#item02 [2] http://pages.adrianba.net/w3c/FilesAndStreams.pdf -- Simon Pieters Opera Software

Re: XPath and find/findAll methods

me/Safari should add support for selectNodes? -- Simon Pieters Opera Software

window.find already exists

/multipage/dnd.html#dom-find Are Firefox and WebKit going to drop the old find()? Is there legacy content that feature detects for find() and would break if it changed semantics? -- Simon Pieters Opera Software

Re: Firefox bug: "Worker" load ignores Content-Type version parameter

type. -- Simon Pieters Opera Software

Re: Firefox bug: "Worker" load ignores Content-Type version parameter

icular when other parts of the platform disagree. Why not? We have context-dependent treatment of MIME types already (e.g. a text/html resource can be treated as a script). -- Simon Pieters Opera Software

Re: Firefox bug: "Worker" load ignores Content-Type version parameter

On Fri, 18 Nov 2011 13:22:42 +0100, Julian Reschke wrote: On 2011-11-18 13:03, Simon Pieters wrote: UTF-8-only for workers is deliberate. I don't see any reason to reject scripts that have other charset. Rejecting the script would mean that some authors can't use workers at a

Re: Firefox bug: "Worker" load ignores Content-Type version parameter

On Fri, 18 Nov 2011 13:03:03 +0100, Boris Zbarsky wrote: On 11/19/11 12:52 AM, Julian Reschke wrote: says. For what it's worth, Gecko's worker loading code runs the same algorithm to determine the charset as the algorithm u

Re: Firefox bug: "Worker" load ignores Content-Type version parameter

On Fri, 18 Nov 2011 12:52:36 +0100, Julian Reschke wrote: If Gecko does that for Workers, that would be a bug. Workers are UTF-8 only. If you are saying that Content-Type: application/javascript;charset=iso-8859-1 ... 0xC3 0xB6 ... should have U+00C3 U+00B6 when used via

Re: innerHTML in DocumentFragment

ossible to make work. How? -- Simon Pieters Opera Software

  1   2   >