On Mon, Dec 5, 2011 at 8:55 PM, Leif Halvard Silli
wrote:
> When you say 'requires': Of course, HTML5 recommends that you declare
> the encoding (via HTTP/higher protocol, via the BOM 'sideshow' or via
> ). I just now also discovered that Validator.nu
> issues an error message if it does not find
On Mon, Dec 5, 2011 at 7:42 PM, Leif Halvard Silli
wrote:
> Last I checked, some of those locales defaulted to UTF-8. (And HTML5
> defines it the same.) So how is that possible? Don't users of those
> locales travel as much as you do? Or do we consider the English locale
> user's as more important
2011-12-07 2:36, Leif Halvard Silli wrote:
This entire thread started with a user problem.
As far as I can see, the problem presented was: “I still frequently
break websites and webapps simply by entering my name (Faruk Ateş).”
What we need to fix such issues is that sites and applications a
Jukka K. Korpela Tue Dec 6 13:27:11 PST 2011
> 2011-12-06 22:58, Leif Halvard Silli write:
>
>> There is now a bug, and the editor says the outcome depends on "a
>> browser vendor to ship it":
>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=15076
>>
>> Jukka K. Korpela Tue Dec 6 00:39:45 PST 201
On Thu, 14 Jul 2011, Tantek �~Gelik wrote:
>
> Some in the microformats community have been making good use of the
> element, e.g. for publishing hCalendar, and implementing
> consuming/converting hCalendar [1] with good success.
>
> It would be great if the element could support expressing
>
On Mon, 4 Jul 2011, Anne van Kesteren wrote:
> I noticed Ian updated the specification, but it seems current
> implementations differ quite wildly. E.g. Gecko happily ignores
>
> Content-Type: text/event-stream;charset=tralala
>
> as does Opera instead of closing the connection. Chrome bites,
On Thu, 23 Jun 2011, Per-Erik Brodin wrote:
>
> Another question was raised in
>
>https://bugs.webkit.org/show_bug.cgi?id=61862#c17
>
> The origin set on the dispatched message events is specified to be the
> "origin of the event stream's URL". Is this the URL passed to the
> EventSource co
2011-12-06 22:58, Leif Halvard Silli write:
There is now a bug, and the editor says the outcome depends on "a
browser vendor to ship it":
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15076
Jukka K. Korpela Tue Dec 6 00:39:45 PST 2011
what is this proposed change to defaults supposed to achi
On Tue, 6 Dec 2011, James Hawkins wrote:
On Tue, Dec 6, 2011 at 1:16 PM, Tab Atkins Jr. wrote:
On Tue, Dec 6, 2011 at 1:14 PM, James Hawkins wrote:
Originally we envisioned using a self-closing tag placed in head for
the intent tag; however, we're now leaning towards not using
self-closing a
On Tue, Dec 6, 2011 at 1:16 PM, Tab Atkins Jr. wrote:
> On Tue, Dec 6, 2011 at 1:14 PM, James Hawkins wrote:
>> Originally we envisioned using a self-closing tag placed in head for
>> the intent tag; however, we're now leaning towards not using
>> self-closing and having the tag be placed in the
On Tue, Dec 6, 2011 at 1:14 PM, James Hawkins wrote:
> Originally we envisioned using a self-closing tag placed in head for
> the intent tag; however, we're now leaning towards not using
> self-closing and having the tag be placed in the body with fallback
> content, e.g., to install an extension
On Tue, Dec 6, 2011 at 1:08 PM, James Graham wrote:
> On Tue, 6 Dec 2011, Anne van Kesteren wrote:
>
>> Especially changing the way is parsed is hairy. Every new element
>> we introduce there will cause a to be implied before it in down-level
>> clients. That's very problematic.
>
>
> Yes, I con
2011-12-06 15:59, NARUSE, Yui wrote:
(2011/12/06 17:39), Jukka K. Korpela wrote:
2011-12-06 6:54, Leif Halvard Silli wrote:
Yeah, it would be a pity if it had already become an widespread
cargo-cult to - all at once - use HTML5 doctype without using UTF-8
*and* without using some encoding dec
On Tue, 6 Dec 2011, Anne van Kesteren wrote:
Especially changing the way is parsed is
hairy. Every new element we introduce there will cause a to be implied
before it in down-level clients. That's very problematic.
Yes, I consider adding new elements to to be very very bad for this
reason
On Tue, 06 Dec 2011 19:00:36 +0100, James Hawkins
wrote:
Off-topic, but I'm curious as to why you decided to propose a new element
this way?
--
Anne van Kesteren
http://annevankesteren.nl/
There is now a bug, and the editor says the outcome depends on "a
browser vendor to ship it":
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15076
Jukka K. Korpela Tue Dec 6 00:39:45 PST 2011
> what is this proposed change to defaults supposed to achieve. […]
I'd say the same as in XML: UTF-8
On Tue, 06 Dec 2011 19:40:20 +0100, Paul Kinlan
wrote:
I would like to add that we also had a long discussion about trying to
re-use the meta element for specifying intents.
The syntax was something like:
http://webintents.org/share"; />
Pros:
* declarative
* use's existing tags so no change
To clarify, my use of the word 'we' below is we the designers of the
API, not the participants of the Web Intents TF.
As stated in the 'API Status' section below, discussions about Web
Intents are ongoing in the TF. In addition, note that nothing is
finalized in the Web Intents API as of yet.
Si
I would like to add that we also had a long discussion about trying to
re-use the meta element for specifying intents.
The syntax was something like:
http://webintents.org/share"; />
Pros:
* declarative
* use's existing tags so no changes to html spec
Cons:
* no multiplicity - can't define mult
*** Overview ***
The W3C Web Intents Task Force is working on the Web Intents API at
public-web-inte...@w3.org: see the bottom of this email for details.
Web Intents is a web platform API that provides client-side service
discovery and inter-application communication. Services register to
handle
On Dec 5, 2011, at 23:06 , Simon Pieters wrote:
> On Mon, 05 Dec 2011 22:19:33 +0100, Brady Eidson wrote:
>
>> I can't find a definitive answer for the following scenario:
>>
>> 1 - A page has a plug-in with fallback specified as follows:
>>
>>
>>
>>
>>
>>
>> 2 - The page is loaded, t
(2011/12/06 17:39), Jukka K. Korpela wrote:
> 2011-12-06 6:54, Leif Halvard Silli wrote:
>
>> Yeah, it would be a pity if it had already become an widespread
>> cargo-cult to - all at once - use HTML5 doctype without using UTF-8
>> *and* without using some encoding declaration *and* thus effective
2011-12-06 6:54, Leif Halvard Silli wrote:
Yeah, it would be a pity if it had already become an widespread
cargo-cult to - all at once - use HTML5 doctype without using UTF-8
*and* without using some encoding declaration *and* thus effectively
relying on the default locale encoding ... Who does
23 matches
Mail list logo
