On Mon, 13 Feb 2012 13:38:49 +0100, L. David Baron dba...@dbaron.org
wrote:
On Monday 2012-02-13 09:00 +0100, Simon Pieters wrote:
Exactly. My proposal, again, is that neither of these quirks
apply inside a shorthand.
But this is not what Gecko does.
On Wed, 20 Jul 2011, Tim Down wrote:
On 6 January 2011 21:53, Ian Hickson i...@hixie.ch wrote:
On Wed, 27 Oct 2010, benjamin.poul...@nokia.com wrote:
I would like to suggest a change for the main HTML 5 specification:
http://www.whatwg.org/specs/web-apps/current-work/
The problem I
On Wed, Feb 15, 2012 at 11:26 AM, Ian Hickson i...@hixie.ch wrote:
So I guess we have to make a decision for the platform here.
Do we want:
- To spec window.find() in all its historical glory, and have it
implemented everywhere?
- To spec a subset of window.find() that just does the
+1 to TJ's mention of find for use in the Selector API:
http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/0277.html
Rick
On Wed, Feb 15, 2012 at 2:49 PM, Tab Atkins Jr. jackalm...@gmail.comwrote:
On Wed, Feb 15, 2012 at 11:26 AM, Ian Hickson i...@hixie.ch wrote:
So I guess we
On Wed, 20 Jul 2011, Justin Lebar wrote:
The spec as written decides whether a link is a same-resource
reference or not based on comparing the URLs to what you're calling
the original address, not comparing it to the current address. See the
navigation algorithm, step 7 /Fragment
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1342
It doesn't make sense that the second image is broken.
(For some reason in Firefox I get an exception. Not sure if I'm misusing
the API or if it's a bug in Firefox.)
Not sure what's going on with that Firefox exception. But
I've shown this proposal to a couple of people here at Apple, and we have no
issues with it. I'm personally eager to see it move forward!
--
Jon
On Dec 15, 2011, at 1:17 PM, Ilya Sherman isher...@chromium.org wrote:
Current autofill products rely on contextual clues to determine the type of
On Wed, 15 Feb 2012, Justin Lebar wrote:
Hm...maybe you're right. But then, how do we jive this with #foo and
?foo links, both of which resolve relative to the current URI in both
Firefox and WebKit?
We fix the implementations to match the spec. :-)
- It sets the document's current
On Fri, 22 Jul 2011, Glenn Maynard wrote:
On Fri, Jul 22, 2011 at 2:58 AM, Ian Hickson i...@hixie.ch wrote:
As Ian says above, if the user is savvy enough to right-click, the
user is likely not going to find it difficult to give the file a name
either.
(But again, just because I'm able
We, the designers of the Web Intents draft API, have always seen Web
Intents as a superset of the functionality provided by
registerProtocolHandler (RPH) and registerContentHandler (RCH). To
follow this to the logical conclusion, we should be able to provide
functionally equivalent counterparts
...as I'm in the middle of a project implementing schema.org markup, is there
any consideration of using those properties as the tokens within the
autocomplete attribute?
While not perfectly compatible, it would lessen the burden on developers—Is it
given-name or givenName for form fields?—and
On Wed, Feb 15, 2012 at 3:57 PM, Nathan Ziarek nzia...@gmail.com wrote:
...as I'm in the middle of a project implementing schema.org markup, is
there any consideration of using those properties as the tokens within the
autocomplete attribute?
While not perfectly compatible, it would lessen
On Wed, Feb 15, 2012 at 5:31 PM, Ian Hickson i...@hixie.ch wrote:
On Wed, 15 Feb 2012, Justin Lebar wrote:
- It sets the document's current address to .../page.html#foo.
Well, this is pretty bad. document.location is the document's current
address [1]. So clicking #foo changed
13 matches
Mail list logo
