Re: Minutes of Shadow DOM meeting

2015-04-25 Thread Bjoern Hoehrmann
* cha...@yandex-team.ru wrote: We'll post a summary - there is most of one at https://docs.google.com/spreadsheets/d/1hnCoaJTXkfSSHD5spISJ76nqbDcOVNMamgByiz3QWLA/edit?pli=1#gid=0 Perhaps a document in some kind of open format would be a better medium than some proprietary application with

Re: CORS performance

2015-02-19 Thread Bjoern Hoehrmann
* Jonas Sicking wrote: We most likely can consider the content-type header as *not* custom. I was one of the people way back when that pointed out that there's a theoretical chance that allowing arbitrary content-type headers could cause security issues. But it seems highly theoretical. I suspect

Re: CORS performance proposal

2015-02-19 Thread Bjoern Hoehrmann
* Martin Thomson wrote: On 20 February 2015 at 00:29, Anne van Kesteren ann...@annevk.nl wrote: Access-Control-Allow-Origin-Wide-Cache: [origin] This has some pretty implications for server deployments that host mutual distrustful applications. Now, these servers are already pretty well hosed

Re: CORS performance proposal

2015-02-19 Thread Bjoern Hoehrmann
* Martin Thomson wrote: On 20 February 2015 at 11:39, Bjoern Hoehrmann derhoe...@gmx.net wrote: The proposal is to use `OPTIONS * HTTP/1.1` not `OPTIONS /x HTTP/1.1`. I missed that. In which case I'd point out that `OPTIONS *` is very poorly supported. Some people (myself included) want

Re: CORS performance

2015-02-17 Thread Bjoern Hoehrmann
* Anne van Kesteren wrote: With the recent introduction of CSP pinning, I was wondering whether something like CORS pinning would be feasible. A way for a server to declare that it speaks CORS across an entire origin. The CORS preflight in effect is a rather complicated way for the server to

Re: CORS performance

2015-02-17 Thread Bjoern Hoehrmann
* Anne van Kesteren wrote: On Tue, Feb 17, 2015 at 8:18 PM, Bjoern Hoehrmann derhoe...@gmx.net wrote: Individual resources should not be able to declare policy for the whole server, ... With HSTS we gave up on that. Well, HSTS essentially removes communication options, while the intent of CORS

Re: Allow custom headers (Websocket API)

2015-02-05 Thread Bjoern Hoehrmann
* Anne van Kesteren wrote: On Thu, Feb 5, 2015 at 2:48 PM, Bjoern Hoehrmann derhoe...@gmx.net wrote: A Websocket connection is established by making a HTTP Upgrade request, and the protocol is HTTP unless and until the connection is upgraded. Sure, but the server can get away with supporting

Re: Allow custom headers (Websocket API)

2015-02-05 Thread Bjoern Hoehrmann
* Anne van Kesteren wrote: On Thu, Feb 5, 2015 at 2:29 PM, Bjoern Hoehrmann derhoe...@gmx.net wrote: It seems to me that pre-flight requests would happen prior to opening a Websocket connection, i.e. before requirements of the Websocket proto- col apply, so this would have to be covered

Re: Shadow tree style isolation primitive

2015-02-05 Thread Bjoern Hoehrmann
* Dimitri Glazkov wrote: Shadow DOM and Web Components seem to have what I call the Unicorn Syndrome. There's a set of specs that works, proven by at least one browser implementation and the use in the wild. It's got warts (compromises) and some of those warts are quite ugly. Those warts weren't

Re: Defining a constructor for Element and friends

2015-01-13 Thread Bjoern Hoehrmann
* Domenic Denicola wrote: From: Bjoern Hoehrmann [mailto:derhoe...@gmx.net] I know that this a major concern to you, but my impression is that few if any other people regard that as anything more than nice to have, especially if you equate explaining with having a public API for it. How do

Re: Defining a constructor for Element and friends

2015-01-13 Thread Bjoern Hoehrmann
* Domenic Denicola wrote: That kind of breaks the design goal that we be able to explain how everything you see in the DOM was constructed. How did the parser (or document.createElement(NS)) create a HTMLUnknownElement, if the constructor for HTMLUnknownElement doesn't work? I know that this a

Re: [editing] Responsive Input Terminology

2014-12-11 Thread Bjoern Hoehrmann
* Ben Peters wrote: There has been a lot of debate [1][2] about the correct name for device independent events [3] as a concept*. We have considered Intention Events, Command Events, and Action Events among others. I believe we now have a good name for them- Responsive Input Events. The reason

Re: I-D Action: draft-lnageleisen-http-chunked-progress-00.txt

2014-04-08 Thread Bjoern Hoehrmann
* internet-dra...@ietf.org wrote: Abstract: This document describes Chunked Progress, an extension to Transfer-Encoding: Chunked as defined in RFC2616 [RFC2616]. Chunked Progress introduces a backwards-compatible, RFC2616 compliant method to notify the client of transfer advancement

Re: [request] Download Event for HTMLAnchorElement

2014-03-25 Thread Bjoern Hoehrmann
* Si Robertson wrote: The problem that this new event would solve is this - when using a temporary object URL (blob) for the file data, e.g. programmatically generated content, there is currently no way of knowing when that file data has been written to disk, therefore there is no reliable way of

Re: On starting WebWorkers with blob: URLs...

2014-03-17 Thread Bjoern Hoehrmann
* Anne van Kesteren wrote: On Fri, Mar 14, 2014 at 10:40 PM, Ian Hickson i...@hixie.ch wrote: On Fri, 14 Mar 2014, Arun Ranganathan wrote: http://dev.w3.org/2006/webapi/FileAPI/#originOfBlobURL LGTM. Assuming that UAs implement this, that makes Workers automatically support blob: URLs, too.

Re: [Bug 24823] New: [ServiceWorker]: MAY NOT is not defined in RFC 2119

2014-02-26 Thread Bjoern Hoehrmann
* bugzi...@jessica.w3.org wrote: The section Worker Script Caching uses the term MAY NOT, which is not defined in RFC 2119. I'm assuming this is intended to be MUST NOT or maybe SHOULD NOT. If an agent MAY $x then it also MAY not $x. It is possible that the author meant must not or should not in

Re: [webcomponents] Encapsulation and defaulting to open vs closed (was in www-style)

2014-02-15 Thread Bjoern Hoehrmann
* Alex Russell wrote: So you've written off the massive coordination costs of adding a uniform to all code across all of Google and, on that basis, have suggested there isn't really a problem? ISTM that it would be a multi-month (year?) project to go patch every project in google3 and then wait

Re: [webcomponents] Encapsulation and defaulting to open vs closed (was in www-style)

2014-02-13 Thread Bjoern Hoehrmann
* Anne van Kesteren wrote: On Thu, Feb 13, 2014 at 12:04 AM, Alex Russell slightly...@google.com wrote: Until we can agree on this, Type 2 feels like an attractive nuisance and, on reflection, one that I think we should punt to compilers like caja in the interim. If toolkits need it, I'd like

Re: [webcomponents] Encapsulation and defaulting to open vs closed (was in www-style)

2014-02-13 Thread Bjoern Hoehrmann
* Maciej Stachowiak wrote: Type 2 is not meant to be a security mechanism. It is meant to be an encapsulation mechanism. Let me give a comparison. Many JavaScript programmers choose to use closures as a way to store private data for objects. That is an encapsulation mechanism. It is not, in

Re: Extending Mutation Observers to address use cases of

2014-02-11 Thread Bjoern Hoehrmann
* Olli Pettay wrote: We could add some scheduling thing to mutation observers. By default we'd use microtask, since that tends to be good for various performance reasons, but normal tasks or nanotasks could be possible too. This sounds like adding a switch that would dynamically invalidate

Re: I need some guidance.

2014-01-20 Thread Bjoern Hoehrmann
* a...@flyingsoft.phatcode.net wrote: Please refer to the following bug report: http://code.google.com/p/chromium/issues/detail?id=336292 In summary, all Webkit-derived browsers (excluding Safari 5.1.7 on Windows) do not do in-process (in-instance?) caching when the header is expired. Firefox,

Re: [manifest] HTTP-based solution for loading manifests

2013-12-11 Thread Bjoern Hoehrmann
* Julian Reschke wrote: On 2013-12-11 19:59, Marcos Caceres wrote: https://github.com/w3c/manifest/issues/98#issuecomment-30293586 I see the comment but I have no idea what he's talking about. The spec is generic; and the IANA registry

Re: [webcomponents] HTML Imports

2013-12-04 Thread Bjoern Hoehrmann
* Anne van Kesteren wrote: On Wed, Dec 4, 2013 at 9:21 AM, Brian Di Palma off...@gmail.com wrote: I would say though that I get the feeling that Web Components seems a specification that seems really pushed/rushed and I worry that might lead to some poor design decisions whose side effects will

Re: [webcomponents] HTML Imports

2013-12-04 Thread Bjoern Hoehrmann
* Brian Di Palma wrote: Neither did I mean it to be taken to mean This work is rushed. I said, I get the feeling that Web Components seems a specification that seems really pushed/rushed, by that I meant it seemed as if the current spec is being pushed as fast as possible toward standardization.

Re: RfC: LCWD of Custom Elements; deadline November 21

2013-12-04 Thread Bjoern Hoehrmann
* Ryosuke Niwa wrote: Now we know that there has been an effort to decouple the various Web Components features and specifications, and the Custom Elements specification was going to the Last Call on its own. Unfortunately, we didn't know about this until fairly recently, which is why our

Re: [HTML Imports]: Sync, async, -ish?

2013-12-03 Thread Bjoern Hoehrmann
* Bryan McQuade wrote: Steve Souders wrote another nice post about this topic: http://www.stevesouders.com/blog/2013/11/26/performance-and-custom-elements/which I recommend reading (read the comments too). That should be  

Re: Regarding: Making the W3C Web SQL Database Specification Active

2013-09-27 Thread Bjoern Hoehrmann
* Michael Fitchett wrote: Since lack of definition is the issue, I would like to recommend a remedy. I know SQL experts and great documentation writers who I would gladly hire to further define the Web SQL Database specification and fill in the missing SQL definition. Is this something that would

Re: [webcomponents]: Changing names of custom element callbacks

2013-07-13 Thread Bjoern Hoehrmann
* Steve Orvell wrote: These callbacks specifically mean the element has entered or left the *document*. We felt that entered/leftDocument was better than insertedInto/removedFromDocument but the key bit is *Document. This has caused enough confusion in discussion that being explicit seems

Re: jar protocol (was: ZIP archive API?)

2013-05-07 Thread Bjoern Hoehrmann
* Anne van Kesteren wrote: On Tue, May 7, 2013 at 7:29 AM, Robin Berjon ro...@w3.org wrote: This isn't very different from JAR but it does have the property of more easily enabling a transition. To give an example, say that the page at http://berjon.com/ contains: link rel=bundle

Re: jar protocol (was: ZIP archive API?)

2013-05-07 Thread Bjoern Hoehrmann
* Robin Berjon wrote: I wonder if we couldn't have a mechanism that would not require a separate URI scheme. Just throwing this against the wall, might be daft: We add a new link relationship: bundle (archive is taken, bikeshed later). The href points to the archive, and there can be as many as

Re: ZIP archive API?

2013-05-07 Thread Bjoern Hoehrmann
* Florian Bösch wrote: It can be implemented by a JS library, but the three reasons to let the browser provide it are Convenience, speed and integration. Convenience is the first reason, since browsers by far and large already have complete bindings to compression algorithms and archive formats,

Re: Fetch: HTTP authentication and CORS

2013-05-04 Thread Bjoern Hoehrmann
* Jonas Sicking wrote: On May 4, 2013 1:29 AM, Anne van Kesteren ann...@annevk.nl wrote: On Fri, May 3, 2013 at 7:00 PM, Jonas Sicking jo...@sicking.cc wrote: We also don't reuse keep-alive http connections. Are we talking about persistent connections as per

Re: [webcomponents]: Of weird script elements and Benadryl

2013-04-17 Thread Bjoern Hoehrmann
* Rick Waldron wrote: On Tue, Apr 16, 2013 at 9:51 PM, Bjoern Hoehrmann derhoe...@gmx.net wrote: * Rick Waldron wrote: If I want to make a new button to put in the document, the first thing my JS programming experience tells me: new Button(); And if you read code like `new A();` your

Re: [webcomponents]: Of weird script elements and Benadryl

2013-04-16 Thread Bjoern Hoehrmann
* Rick Waldron wrote: Of course, but we'd also eat scraps from the trash if that was the only edible food left on earth. document.createElement() is and has always been the wrong way—the numbers shown in those graphs are grossly skewed by a complete lack of any real alternative. If I want to make

Re: Fixing appcache: a proposal to get us started

2013-03-26 Thread Bjoern Hoehrmann
* Jonas Sicking wrote: There has been a lot of debating about fixing appcache. Last year mozilla got a few people together mostly with the goal of understanding what the actual problems were. The notes from that meeting are available at [1]. (I take it the fixing-appcache mailing list has since

Re: IndexedDB, what were the issues? How do we stop it from happening again?

2013-03-14 Thread Bjoern Hoehrmann
* Alex Russell wrote: My *first* approach to this annoyance would be to start adding some async primitives to the platform that don't suck so hard; e.g., Futures/Promises. Saying that you should do something does not imply that doubling up on API surface area for a corner-case is the right

FYI: JSON mailing list and BoF

2013-02-18 Thread Bjoern Hoehrmann
* Joe Hildebrand (jhildebr) wrote: We're planning on doing a BoF in Orlando to discuss starting up a JSON working group. The BoF is currently planned for Monday afternoon at 1300 in Carribean 6. A very preliminary version of a charter can be found here:

FYI: Possible RFC 6455 (WebSocket) throttling erratum

2013-02-14 Thread Bjoern Hoehrmann
Hi, http://www.ietf.org/mail-archive/web/hybi/current/msg09970.html is re http://www.ietf.org/mail-archive/web/hybi/current/msg09961.html about an ambiguity in RFC 6455 regarding how implementations are to limit con- current WebSocket connections. A particular point that has been raised is

Re: Shadow DOM: events that are stopped

2013-02-07 Thread Bjoern Hoehrmann
* Anne van Kesteren wrote: Instead of having a fixed list of events that are stopped, maybe instead we can pass a flag to the dispatch algorithm with respect to whether or not the event being dispatched should exit the shadow boundary it started in, if any. That way you can have your own private

Re: [Clipboard API] Add a flag to indicate paste-as-text to beforepaste and paste events

2012-08-23 Thread Bjoern Hoehrmann
* Ryosuke Niwa wrote: *Proposal* Add a boolean flag to beforepaste and paste events indicating whether the user had intended to paste as text or rich text. (pasteAsText IDL attribute?) There are many more intents here than text and not text, like they may mean to paste vector paths to preseve

Re: Should MutationObservers be able to observe work done by the HTML parser?

2012-06-20 Thread Bjoern Hoehrmann
* Jonas Sicking wrote: I can't think of any cases where you would *not* want these to fire for parser mutations. For example if you are building an XBL-like widget library which uses the DOM under a node to affect behavior or rendering of some other object. If you attach the widget before the

Re: Updates to Selectors API

2012-06-14 Thread Bjoern Hoehrmann
* Lachlan Hunt wrote: At this stage, we should be able to publish v1 as a revised CR, or possibly move it up to PR. We can also publish v2. as a new WD. It does not seem that additional implementation experience is required to make sure no major changes are needed, so, Proposed Recommendation.

Re: www-dom vs public-webapps WAS: [DOM4] Mutation algorithm imposed order on document children

2012-06-13 Thread Bjoern Hoehrmann
* Ojan Vafai wrote: This confusion seems to come up a lot since DOM is part of public-webapps but uses a separate mailing list. Maybe it's time to reconsider that decision? It's the editors of the specs who have the largest say here IMO. The confusion is not going to go away by changing the

Re: [webcomponents] HTML Parsing and the template element

2012-06-11 Thread Bjoern Hoehrmann
* Rafael Weinstein wrote: I think looking at this as whether we are breaking the correspondance between source and DOM may not be helpful -- because it's likely to be a matter of opinion. I'd like to suggest that we look at more precise issues. There are several axes of presence for elements WRT

Re: [Process] Publishing use cases and requirements as official docs

2012-06-06 Thread Bjoern Hoehrmann
* Tobie Langel wrote: Hi, (Starting a new thread by replying to a mail and then changing the subject and quoted text is not a good idea; just start a new mail.) I recently stumbled upon a number of use case and requirements docs (such as MediaStream Capture Scenarios[1] or HTML Speech XG[2])

Re: [Process] Publishing use cases and requirements as official docs

2012-06-06 Thread Bjoern Hoehrmann
* Tobie Langel wrote: On Jun 6, 2012, at 8:46 PM, Bjoern Hoehrmann derhoe...@gmx.net wrote: Only documents under http://www.w3.org/TR/ are official publications as far as Working Group's Technical Reports go. Can't WG release notes? Working Groups can publish Working Group Notes as Technical

Re: [webcomponents] Custom Elements Spec

2012-05-08 Thread Bjoern Hoehrmann
* Anne van Kesteren wrote: I don't think that's really the argument. The argument is about whether the long tail is going to be accessible (even if only a little bit) or not at all. That is, do we get select is=restricted-color-pickeroption value=Redoption value=Blue/select styled as a

Re: CfC: Add warnings to old DOM specifications; deadline April 18

2012-04-04 Thread Bjoern Hoehrmann
* Arthur Barstow wrote: Msger's (Mozilla) proposed text is in the following document and this is a Call for Consensus to agree on this text. If this CfC passes, the text will be added to the top of the Recommendations as was done with [D2V]:

Re: (aside) MIME type

2012-02-21 Thread Bjoern Hoehrmann
* Mark Baker wrote: I wish they did, consistently. See RFC 4288 (just media type) and the registry itself (MIME media type) http://www.iana.org/assignments/media-types/index.html. Plus they're still routinely referred to as MIME types in many IETF contexts, including the ietf-types list!

Re: CG for Speech JavaScript API

2012-01-31 Thread Bjoern Hoehrmann
* Glen Shires wrote: We at Google propose the formation of a new Community Group to pursue a JavaScript Speech API. Specifically, we are proposing this Javascript API [1], which enables web developers to incorporate speech recognition and synthesis into their web pages, and supports the majority

Re: Obsolescence notices on old specifications, again

2012-01-24 Thread Bjoern Hoehrmann
* Glenn Adams wrote: That doesn't really work for me. What would work for me is something like: Although DOM Level 2 continues to be subject to Errata Managementhttp://www.w3.org/2005/10/Process-20051014/tr.html#errata, it is no longer being actively maintained. Content authors and implementers

Re: Obsolescence notices on old specifications, again

2012-01-23 Thread Bjoern Hoehrmann
* Ms2ger wrote: The recent message to www-dom about DOM2HTML [1] made me realize that we still haven't added warnings to obsolete DOM specifications to hopefully avoid that people use them as a reference. If you want to say more than that the specifications are no longer being maintained and

Re: [XHR] responseType json

2012-01-06 Thread Bjoern Hoehrmann
* Jarred Nicholls wrote: This is an editor's draft of a spec, it's not a recommendation, so it's hardly a violation of anything. This is a 2-way street, and often times it's the spec that needs to change, not the implementation. The point is, there needs to be a very compelling reason to breach

Re: [XHR] upload progress events (successfully uploaded)

2011-12-23 Thread Bjoern Hoehrmann
* Anne van Kesteren wrote: I plan on making these two changes: * Instead of saying If the request entity body has been successfully uploaded I will say If the request entity body has been fully transmitted to make it clear we do not need to wait for the response. I think that was the

Re: [XHR] responseType json

2011-12-05 Thread Bjoern Hoehrmann
* Glenn Adams wrote: What do you mean by treat content that clearly is UTF-32 as UTF-16-encoded? Do you mean interpreting it as a sequence of unsigned shorts? That would be a direct violation of the semantics of UTF-32, would it not? Consider you have ... Content-Type:

Re: [XHR] responseType json

2011-12-04 Thread Bjoern Hoehrmann
* Anne van Kesteren wrote: I tied it to UTF-8 to further the fight on encoding proliferation and encourage developers to always use that encoding. The fight here is for standards. You know, you read the specification, create some content, and then that content works in all implementations that

Re: [XHR] responseType json

2011-12-04 Thread Bjoern Hoehrmann
* Henri Sivonen wrote: Browsers don't support UTF-32. It has no use cases as an interchange encoding beyond writing evil test cases. Defining it as a valid encoding is reprehensible. If UTF-32 is bad, then it should be detected as such and be rejected. The current idea, from what I can tell, is

Re: XPath and Selectors are identical, and shouldn't be co-developed

2011-11-30 Thread Bjoern Hoehrmann
* Tab Atkins Jr. wrote: Disclaimer: I'm a CSSWG member, was previously a web developer by trade (now am a webkit engineer/spec author), and was only vaguely aware of XPath a week ago. XPath support has been available in web browsers for over decade. If you have so far been unaware of it, that

Re: XPath and Selectors are identical, and shouldn't be co-developed

2011-11-30 Thread Bjoern Hoehrmann
* Yehuda Katz wrote: Most people would accomplish that using jQuery. Something like: var previous = $(current).closest(tr).prev() I'm not exactly sure what `current` is in this case. What edge-cases are you worried about when you say that the JavaScript is quite involved? It is unlikely that

Re: XPath and Selectors are identical, and shouldn't be co-developed

2011-11-30 Thread Bjoern Hoehrmann
* Yehuda Katz wrote: Out of curiosity, I'd like to see the DOM in question, the starting element and the element you were trying to select. I think how people do it in the real world is actually relevant. There is a table for each album and in an album each tbody/tr element is a track in that

Re: XPath and find/findAll methods

2011-11-25 Thread Bjoern Hoehrmann
* Robin Berjon wrote: If no one else steps up to it I can, but I was under the impression that our good friends from Opera had a solution they could contribute — I would hope in the shape of an editor :) I started it some years ago, but then figured if anybody brought it up the selectors shirts

Re: XPath and find/findAll methods

2011-11-22 Thread Bjoern Hoehrmann
* Tab Atkins Jr. wrote: I know you're being somewhat hostile because you like XPath and we're essentially saying ignore XPath, it's dead, but still, you're arguing badly. The web platform has a single selection syntax that has won without question. When Robin starts referring to himself in the

Re: XPath and find/findAll methods

2011-11-22 Thread Bjoern Hoehrmann
* Tab Atkins Jr. wrote: Come on, Robin, you're being unreasonable. You and I both know there's a huge difference between new features require small amounts of new syntax and oh look, it's an entirely different language. I can't make heads or tails of the 'nth' syntax despite implementing it a

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

2011-11-19 Thread Bjoern Hoehrmann
* Simon Pieters wrote: Workers ignore the MIME type. Yes, this thread was initially about the problems that causes. -- Björn Höhrmann · mailto:bjo...@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub.

Re: Synchronous postMessage for Workers?

2011-11-18 Thread Bjoern Hoehrmann
* Joshua Bell wrote: Jonas and I were having an offline discussing regarding the synchronous Indexed Database API and noting how clean and straightforward it will allow Worker scripts to be. One general Worker issue we noted - independent of IDB - was that there are cases where Worker scripts may

Re: TAG Comment on

2011-11-15 Thread Bjoern Hoehrmann
* Tab Atkins Jr. wrote: On Tue, Nov 15, 2011 at 5:28 PM, Glenn Adams gl...@skynav.com wrote: Perhaps. But widely implemented does not necessarily imply widely used. In any case, support for or use of a feature of a WD or CR does not imply it must be present in REC. Use of a feature does, in

Re: What type should .findAll return

2011-11-11 Thread Bjoern Hoehrmann
* Tab Atkins Jr. wrote: Could you point me to an explanation of what [[Class]] represents in ecmascript? It's a little hard to search for. http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf Section 8.6.2. for instance. -- Björn Höhrmann · mailto:bjo...@hoehrmann.de ·

Re: Enable compression of a blob to .zip file

2011-10-30 Thread Bjoern Hoehrmann
* Cameron McCormack wrote: On 30/10/11 10:54 AM, Charles Pritchard wrote: One reason I've needed inflate is for svgz support. Browser vendors have consistently left bugs and/or ignored the spec for handling svgz files. SVG is really intended to be deflated. All major browsers have support for

Re: QSA, the problem with :scope, and naming

2011-10-25 Thread Bjoern Hoehrmann
* Tab Atkins Jr. wrote: Did you not understand my example? el.find(+ foo, + bar) feels really weird and I don't like it. I'm okay with a single selector starting with a combinator, like el.find(+ foo), but not a selector list. Allowing + foo but not + foo, + bar would be really weird. -- Björn

Re: QSA, the problem with :scope, and naming

2011-10-25 Thread Bjoern Hoehrmann
* Tab Atkins Jr. wrote: On Tue, Oct 25, 2011 at 4:56 PM, Ojan Vafai o...@chromium.org wrote: On Tue, Oct 25, 2011 at 4:44 PM, Bjoern Hoehrmann derhoe...@gmx.net wrote: * Tab Atkins Jr. wrote: Did you not understand my example?  el.find(+ foo, + bar) feels really weird and I don't like it.  I'm

Re: QSA, the problem with :scope, and naming

2011-10-20 Thread Bjoern Hoehrmann
* Alex Russell wrote: I strongly agree that it should be an Array *type*, but I think just returning a plain Array is the wrong resolution to our NodeList problem. WebIDL should specify that DOM List types *are* Array types. It's insane that we even have a NodeList type which isn't a real array at

Re: [DOM4] XML lang

2011-10-05 Thread Bjoern Hoehrmann
* Marcos Caceres wrote: 1. I need to find elements of a particular type/name that are in a particular language (in tree order), so that I can extract that information to display to a user. .selectNodes(//type[lang('language')]) 2. I need to check what the language of an element is (if any),

Re: Adding Web Intents to the Webapps WG deliverables

2011-09-20 Thread Bjoern Hoehrmann
* Ian Fette wrote: I don't get it. The overhead of getting all the other browsers to join the WG you mention is just as high, especially when there's no indication that a number of browsers intend to join that group. I don't think it's a random process question, I think it's rather fundamental

Re: [DOM4] Remove Node.isSameNode

2011-09-09 Thread Bjoern Hoehrmann
* Jonas Sicking wrote: It's a completely useless function. It just implements the equality operator. I believe most languages have a equality operator already. It's quite normal for object models to not guarantee that the equality operator works for object identity comparison, COM being a prime

Re: Reference to the HTML specification

2011-09-06 Thread Bjoern Hoehrmann
* Julian Reschke wrote: I do see that it's a problem when people use outdated specs; but maybe the problem is not the being dated, but how they are published. As far as I can tell, there's not nearly as much confusion on the IETF side of things, where Internet Drafts actually come with an

Re: From-Origin FPWD

2011-07-31 Thread Bjoern Hoehrmann
* Anne van Kesteren wrote: http://www.w3.org/TR/from-origin/ The proposed `From-Origin` header conveys a subset of the information that is already available through the Referer header. As it is, it is very rare for the Referer header, or coressponding interfaces that are available to scripts,

Re: Mutation events replacement

2011-07-20 Thread Bjoern Hoehrmann
* Dave Raggett wrote: Perhaps we need to distinguish auto generated attributes from those that are set by markup or scripts. Could you please clarify for me the difference between the html style attribute and the one you are referring to? My understanding is that the html style attribute is

Re: Mutation events replacement

2011-07-20 Thread Bjoern Hoehrmann
* Boris Zbarsky wrote: It's pretty common to have situations where lots (10-20) of properties are set in inline style, especially in cases where the inline style is being changed via CSS2Properties from script (think animations and the like, where the objects being animated tend to have width,

Re: Mutation events replacement

2011-07-20 Thread Bjoern Hoehrmann
* Boris Zbarsky wrote: On 7/20/11 2:19 PM, Bjoern Hoehrmann wrote: Depending on the design of the mutation notification system and what level of complexity people find palatable, it would naturally also be possible to serialize lazily The only way to do that is to make sure the pre-mutation

Re: [websockets] Reminder: review Web Socket Protocol v10; deadline July 25

2011-07-19 Thread Bjoern Hoehrmann
* Arthur Barstow wrote: A reminder to review the Web Socket Protocol v10 spec by July 25: https://datatracker.ietf.org/doc/draft-ietf-hybi-thewebsocketprotocol/ http://www.ietf.org/id/draft-ietf-hybi-thewebsocketprotocol-10.txt Individual WG members are encouraged to provide individual

Re: XHR using user and password parameters

2011-07-11 Thread Bjoern Hoehrmann
* Hallvord R. M. Steen wrote: Many implementations don't send the Authorize: header even if the script supplies user name and password, unless they have seen a 401 response. This seems a bit counter-intuitive to authors - if they supply a user name and a password, why isn't the browser

Re: [websockets] IETF HyBi current status and next steps

2011-07-11 Thread Bjoern Hoehrmann
* Arthur Barstow wrote: Is there a deadline for protocol comments? Based on the e-mail below, it appears the deadline is July 25. Please clarify. The IESG is asking for comments by that date. There will be some time between the date and the IESG making its decision, and there will be some time

Re: Test suites and RFC2119

2011-07-10 Thread Bjoern Hoehrmann
* Aryeh Gregor wrote: The difference is that if you have must requirements that are specific to a single conformance class, you can write a test suite and expect every implementation in that class to pass it. For should requirements, you're saying it's okay to violate it, so test suites don't

Re: Publishing From-Origin Proposal as FPWD

2011-07-05 Thread Bjoern Hoehrmann
* Marcos Caceres wrote: On Tue, Jul 5, 2011 at 5:50 PM, Hill, Brad bh...@paypal-inc.com wrote: I feel that the goals of this draft are either inconsistent with the basic architecture of the web, cannot be meaningfully accomplished by the proposed mechanism, or both, and I haven't seen any

Re: Reminder: RfC: Last Call Working Draft of Web Workers; deadline April 21

2011-04-21 Thread Bjoern Hoehrmann
* Tab Atkins Jr. wrote: Please correct me if I'm missing something, but I don't see any new privacy-leak vectors here. Without Shared Workers, 3rdparty.com can just hold open a communication channel to its server and shuttle information between the iframes on A.com and B.com that way. That does

Re: [IndexedDB] Spec changes for international language support

2011-02-18 Thread Bjoern Hoehrmann
* Pablo Castro wrote: We discussed international language support last time at the TPAC and I said I'd propose spec text for it. Please find the patch below, the changes mirror exactly the proposal described in the bug we have for tracking this: http://www.w3.org/Bugs/Public/show_bug.cgi?id=9903

Re: Structured clone in WebStorage

2010-12-02 Thread Bjoern Hoehrmann
* Tab Atkins Jr. wrote: I won't be the person implementing it, but fwiw I highly value having structured clones actually work. Any time I talk about localStorage or similar, I get people asking about storing non-string data, and not wanting to have to futz around with rolling their own

Re: [ProgressEvents] How to deal with compressed transfer encodings

2010-11-23 Thread Bjoern Hoehrmann
* Anne van Kesteren wrote: On Tue, 23 Nov 2010 22:41:00 +0100, Jonas Sicking jo...@sicking.cc wrote: A) Set total to 0, and loaded to the number of decompressed bytes downloaded so far B) Set total to the contents of the Content-Length header and loaded the number of compressed bytes

Re: [ProgressEvents] How to deal with compressed transfer encodings

2010-11-23 Thread Bjoern Hoehrmann
* Jonas Sicking wrote: How should ProgressEvents deal with compressed transfer encodings? The problem is that the Content-Length header (if I understand things correctly) contains the encoded number of bytes, so we don't have access to the total number of bytes which will be exposed to the user

Re: requestAnimationFrame

2010-11-23 Thread Bjoern Hoehrmann
* Robert O'Callahan wrote: Couldn't is never an issue here. You can always use setTimeout as a backstop to ensure that your end-of-animation code runs even if requestAnimationFrame never fires a callback. My concern is that authors are likely to forget to do this even if they need to, because

Re: [cors] 27 July 2010 CORS feedback

2010-11-23 Thread Bjoern Hoehrmann
* Jonas Sicking wrote: other person: Hmm.. we might want to disable cross-site posting for forms some day, so is it such a good idea that cors enables it? me: If we do disable it for forms we'll just disable it for cors too. So much content will break for forms that the cors breakage won't be what

Re: [cors] 27 July 2010 CORS feedback

2010-11-23 Thread Bjoern Hoehrmann
* Jonas Sicking wrote: On Tue, Nov 23, 2010 at 7:36 PM, Bjoern Hoehrmann derhoe...@gmx.net wrote: At the point where browser vendors actually disable cross site form posts it won't break a lot of sites, since browser vendors are not in the habit of making changes that break a lot of sites

Re: requestAnimationFrame

2010-11-19 Thread Bjoern Hoehrmann
* Ojan Vafai wrote: On Fri, Nov 19, 2010 at 2:54 PM, Cameron McCormack c...@mcc.id.au wrote: Darin Fisher: I can imagine a situation where you have an animation that goes for, say, 10 seconds, and once the animation finishes something else happens. The 1 second maximum period seems useful in

Re: requestAnimationFrame

2010-11-19 Thread Bjoern Hoehrmann
* Robert O'Callahan wrote: Those are good goals, except I think we need to drill down into (c). Are people changing stuff at 15Hz for crude performance tuning, or for some other reason? There are many kinds of animations where you cannot easily interpolate between frames, so drawing in Ones

Re: [Bug 11351] New: [IndexedDB] Should we have a maximum key size (or something like that)?

2010-11-19 Thread Bjoern Hoehrmann
* Jonas Sicking wrote: The question is in part where the limit for ridiculous goes. 1K keys are sort of ridiculous, though I'm sure it happens. By ridiculous I mean that common systems would run out of memory. That is different among systems, and I would expect developers to consider it up to an

Re: requestAnimationFrame

2010-11-15 Thread Bjoern Hoehrmann
* Jonas Sicking wrote: On Mon, Nov 15, 2010 at 5:01 PM, Bjoern Hoehrmann derhoe...@gmx.net wrote: The frame rate is a number in the swf header that cannot be set to a as fast as possible value. Ah, so that also means that different animations can't run with different frame rates? That's

Re: Making non-cookie requests to another domain... possible DoS attack by forcing session expiration?

2010-11-10 Thread Bjoern Hoehrmann
* Jonas Sicking wrote: It was brought up by Billy Hoffman (http://zoompf.com) that some web applications have very sensitive sessions and they are set up to expire the session (ie, log the person out) if a request is received that has no session cookie header in it, etc. The assertion was that

Re: XHR responseArrayBuffer attribute: suggestion to replace asBlob with responseType

2010-11-10 Thread Bjoern Hoehrmann
* David Flanagan wrote: Is this a fair summary of this thread? Chris (Apple) worries that having to support both responseText and responseArrayBuffer will be memory inefficient because implementations will end up with both representations in memory. James (Google) worries that synchronously

Re: XHR responseArrayBuffer attribute: suggestion to replace asBlob with responseType

2010-11-10 Thread Bjoern Hoehrmann
* Jonas Sicking wrote: In most cases you do not need to store the bytes in order to get them back, you can just apply the character encoding scheme used to decode the bytes to the string and you'll have the original byte string, so long as the character encoding scheme is bijective, which is

Re: XHR responseArrayBuffer attribute: suggestion to replace asBlob with responseType

2010-11-10 Thread Bjoern Hoehrmann
* Boris Zbarsky wrote: On 11/10/10 4:39 PM, Bjoern Hoehrmann wrote: In most cases you do not need to store the bytes in order to get them back, you can just apply the character encoding scheme used to decode the bytes to the string and you'll have the original byte string, so long

  1   2   >