[whatwg] Update on fallback encoding findings

for now. I'm willing to reconsider if another browser (that has high market share in China) successfully starts using the gb18030 encoder for form submissions for sites that declare gbk (or gb2312) or don't declare an encoding. -- Henri Sivonen hsivo...@hsivonen.fi https://hsivonen.fi/

Re: [whatwg] Guessing the fallback encoding from the top-level domain name before trying to guess from the browser localization

the wrong fallback. (These wrong fallbacks are fixed in Firefox 28. In Firefox 28, no locale falls back to UTF-8.) -- Henri Sivonen hsivo...@hsivonen.fi https://hsivonen.fi/

Re: [whatwg] Guessing the fallback encoding from the top-level domain name before trying to guess from the browser localization

? It hasn't been an obvious and immediate disaster. -- Henri Sivonen hsivo...@hsivonen.fi https://hsivonen.fi/

[whatwg] Guessing the fallback encoding from the top-level domain name before trying to guess from the browser localization

are hosted under a foreign TLD, because the TLD looks cool (e.g. .io). However, this is a relatively new phenomenon, so one might hope that there's less content authored according to legacy practices involved. * This probably lowers the incentive to declare the legacy encoding a little. -- Henri

[whatwg] Add an attribute for opting out of synchronous CSSOM access

even after zooming or invoking a print function * makes the sheet load with low priority and not defer the load event if its media query does not match at the time the link element is inserted into the document but might match later (e.g. if it's a print style sheet). -- Henri Sivonen hsivo

[whatwg] Requiring the Encoding Standard preferred name is too strict for no good reason

suggestion. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] menu and friends

identifier in the future if a non-void element with a command-like name is needed in the future? -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] We should not throw DOM Consistency and Infoset compatibility under the bus

On Fri, Jan 11, 2013 at 10:00 PM, Ian Hickson i...@hixie.ch wrote: On Fri, 11 Jan 2013, Henri Sivonen wrote: I understand that supporting XML alongside HTML is mainly a burden for browser vendors and I understand that XML currently doesn't get much love from browser vendors. Not just browser

[whatwg] We should not throw DOM Consistency and Infoset compatibility under the bus

that it would no longer fit into the XML data model *as implemented* and thereby limit the range of existing software that could be used outside browsers for working with HTML just because XML in browsers is no longer in vogue. Please, let's not make that mistake. -- Henri Sivonen hsivo...@iki.fi http

Re: [whatwg] menu and friends

of command from parsing or serialization. Could you, please, revert the serializing algorithm to treat command as void and menuitem as non-void? -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Question on Limits in Adaption Agency Algorithm

On Sat, Dec 8, 2012 at 11:05 PM, Ian Hickson i...@hixie.ch wrote: the order between abc and xyz is reversed in the tree. Does anyone have any preference for how this is fixed? Does it need to be fixed? That is, is it breaking real sites? -- Henri Sivonen hsivo...@iki.fi http

Re: [whatwg] [mimesniff] Sniffing archives

is inadequate, because you really don’t want to offer to unzip EPUB, ODF, OOXML, XPS, InDesign, etc. files. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Loading and executing script as quickly as possible using multipart/mixed

some sort of identifier for which the author can tell which chunk executed. If the script author needs to manually designate the chunk boundaries, can’t the script authors insert a call to a function before each boundary? That is, why is it necessary for the UA to generate events? -- Henri

Re: [whatwg] [mimesniff] Handling container formats like Ogg

for handling it as part of sniffing layer? -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] main element parsing behaviour

not a fan of the consequences of the “feature” of making /p optional. Too bad that feature is ancient and it’s too late on undo it.) I guess I’ll focus on objecting to new void elements and especially to new children of head. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] maincontent element spec updated and supporting data provided

, it won't have a p element preceding it anyway. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Archive API - proposal

tests if the byte string is a valid UTF-8 string. If it is, the byte string is interpreted as UTF-8 when converting to UTF-16. If the filename is not a valid UTF-8 string, it is decoded into UTF-16 using the fallback encoding. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] [selectors4] drag-and-drop pseudo-classes

On Aug 14, 2012 10:54 PM, Tab Atkins Jr. jackalm...@gmail.com wrote: On Tue, Aug 14, 2012 at 12:13 PM, Ryosuke Niwa rn...@webkit.org wrote: Yeah, and that's not compatible with how drag and drop are implemented on the Web. I know. You'll notice that I didn't suggest we somehow change to

Re: [whatwg] Was is considered to use JSON-LD instead of creating application/microdata+json?

there. It means that JSON-LD requires more consumer complexity than application/microdata+json. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Features for responsive Web design

for the non-art-directed case. Ian Hickson wrote: On Wed, 16 May 2012, Henri Sivonen wrote: It seems to me that Media Queries are appropriate for the art-direction case and factors of the pixel dimensions of the image referred to by src= are appropriate for the pixel density case. I'm

Re: [whatwg] register*Handler and Web Intents

algorithm. Let's not break what we've achieved to cater to aesthetics. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] alt= and the meta name=generator exception

=, so it's easy to shy away from using it on imagined efficiency grounds. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] alt= and the meta name=generator exception

interpret the measurements? -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Linters should complain about missing accessible names for controls [Was: Re: alt= and the meta name=generator exception]

for photos etc - maybe even non-existent - and when hand-authoring describing a control is even easier than coming up with a text equivalent for a graphic. Yeah. In this case, the problem isn't non-interactive generators but interactive editors. -- Henri Sivonen hsivo...@iki.fi http

Re: [whatwg] Load events fired during onload handlers

that fires DOMContentLoaded. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] register*Handler and Web Intents

) Rename intent to link 2) Rename intent to meta 3) Make intent have an end tag and make it placed in body rather than head I prefer solution #1. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] alt and title attribute exception

attribute to convey important information. Indeed. In addition to image considerations, I think http://www.whatwg.org/specs/web-apps/current-work/#footnotes is bad advice. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] alt= and the meta name=generator exception

with the default settings and, therefore, what you suggest wouldn't fix the problem that the spec is trying to fix. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Proposal for readyState behavior

be: https://www.w3.org/Bugs/Public/show_bug.cgi?id=14689 I don't think you need to spec infrastructure to define a high-level expectation that loads with XSLT errors are supposed to finish as if they were successful loads rather than aborted loads. -- Henri Sivonen hsivo...@iki.fi http

Re: [whatwg] Readiness of script-created documents

of the following code pattern causing doStuff to run once the document has completely loaded: if (document.readyState == complete) { setTimeout(doStuff, 0); } else { document.addEventListener(load, doStuff); } -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] HTMLLinkElement.disabled and HTMLLinkElement.sheet behavior

On Thu, Jun 7, 2012 at 2:47 AM, Ian Hickson i...@hixie.ch wrote: On Fri, 27 Jan 2012, Boris Zbarsky wrote: On 1/27/12 1:30 AM, Ian Hickson wrote: On Wed, 5 Oct 2011, Henri Sivonen wrote: On Tue, Oct 4, 2011 at 9:54 PM, Boris Zbarskybzbar...@mit.edu  wrote: What Firefox does do is block

Re: [whatwg] Various HTML element feedback

defines paragraph in a way that doesn't depend on p.) Is there any known example of a piece of software that needs to care about the concept of paragraph and uses the rules given in the spec for determining what constituted paragraphs? -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Media queries, viewport dimensions, srcset and picture

compression.) -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Bandwidth media queries

as the everything except images have loaded and the dimensions of all image boxes are known to the CSS formatter (and PNG and JPEG progression is used 1990s style after the load even has fired). -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Features for responsive Web design

educated people do dpi math right even when an inch is a real inch an not an abstraction.) -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] IBM864 mapping of Encoding Standard

fonts were hidden from Web content and UTF-7 was made mail-only. If OS/2 doesn't need it for system APIs, can we just remove the IBM864 support altogether. Is the AIX port still relevant? I thought 3.6 was the last version ported to AIX. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Encoding Sniffing

be bothered to use The Encoding deserve REPLACEMENT CHARACTERs. Heuristic detection is for unlabeled legacy content. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Readiness of script-created documents

On Mon, Jun 20, 2011 at 3:10 PM, Jonas Sicking jo...@sicking.cc wrote: On Mon, Jun 20, 2011 at 4:26 AM, Henri Sivonen hsivo...@iki.fi wrote: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1039 It says complete in Firefox, loading in Chrome and Opera and uninitialized in IE

[whatwg] Proposal for readyState behavior

/window-stop.html Documents aborted by window.location reach complete in Opera: http://hsivonen.iki.fi/test/moz/readystate/window-location.html Defer scripts are executed at the wrong time in Firefox: http://hsivonen.iki.fi/test/moz/readystate/defer-script.html -- Henri Sivonen hsivo...@iki.fi http

Re: [whatwg] DOMContentLoaded, load and current document readiness

On Tue, Jan 10, 2012 at 2:10 AM, Ian Hickson i...@hixie.ch wrote: On Tue, 31 May 2011, Henri Sivonen wrote: Recently, there was discussion about changing media element state in the same task that fires the event about the state change so that scripts that probe the state can make non-racy

Re: [whatwg] readyState transitions when aborting a document

On Thu, Apr 19, 2012 at 2:43 PM, Henri Sivonen hsivo...@iki.fi wrote:  * Is there a way to abort a document load in IE without causing immediate navigation away from the document? IE doesn't support window.stop(). Yes. document.execCommand(Stop)  * Does Web compatibility ever require

[whatwg] readyState transitions when aborting a document

window.stop() really not abort the parser like the spec seems to suggest? * Should reaching complete always involve firing load? * Should reaching interactive always involve firing DOMContentLoaded? * Does anyone have test cases for this stuff? -- Henri Sivonen hsivo...@iki.fi http

Re: [whatwg] Default encoding to UTF-8?

in some cases. On IRC (#whatwg) zcorpan pointed out this would break URLs where entities are used to encode non-ASCII code points in the query component. Good point. So it's not worthwhile to add magic here. It's better that authors declare that they are using UTF-8. -- Henri Sivonen hsivo

Re: [whatwg] Readiness of script-created documents

not worthwhile to spend time trying to get the behavior to change from what was initially introduced. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Default encoding to UTF-8?

that this thread hasn't gained a message explaining what Chrome does exactly. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Readiness of script-created documents

On Fri, Mar 30, 2012 at 8:26 PM, Jonas Sicking jo...@sicking.cc wrote: On Friday, March 30, 2012, Henri Sivonen wrote: On Fri, Jan 13, 2012 at 2:26 AM, Ian Hickson i...@hixie.ch wrote: Jonas is correct. Since there was no interop here I figured we might as well go with what made sense

Re: [whatwg] Readiness of script-created documents

On Mon, Apr 2, 2012 at 10:12 AM, Henri Sivonen hsivo...@iki.fi wrote: Gratuitously changing features introduced by IE does not help authors one day have to ...when they have to... -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Character-encoding-related threads

to the error console when submitting a form using an encoding that cannot represent all Unicode. Hopefully, after Firefox 12 has been released, this will help Web authors to actually test their sites with the error console open locate forms that can corrupt user input. On Wed, 7 Dec 2011, Henri Sivonen

Re: [whatwg] window.location aborting the parser and subsequent document.writes

On Tue, Feb 14, 2012 at 2:43 AM, Ian Hickson i...@hixie.ch wrote: On Thu, 5 Jan 2012, Henri Sivonen wrote: Consider https://bug98654.bugzilla.mozilla.org/attachment.cgi?id=77369 with the popup blocker disabled. Chrome, Opera and IE open a new window/tab and load the Mozilla front page

Re: [whatwg] Client side value for language preference

that much? -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] RWD Heaven: if browsers reported device capabilities in a request header (Boris Zbarsky)

be improved by Opera Mini, Safari, Amazon's browsers and Google's browsers saying Tablet when on tablet. Symbian is dead, so no hope for its stock browser starting to say Mobi. The inferences you may want to make from the form factor data may well be wrong. -- Henri Sivonen hsivo...@iki.fi http

Re: [whatwg] Client side value for language preference

. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Readiness of script-created documents

good. When trying to make it better, I discovered that doing what IE did would have lead to simpler code. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] API for encoding/decoding ArrayBuffers into text

functions. If we deem streaming conversion unnecessary, I'd put the methods on DOMString and ArrayBufferView. It would be terribly sad to let the schedules of various working groups affect the API design. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] RWD Heaven: if browsers reported device capabilities in a request header

* to tie other side effects to this negotiation, but it doesn't mean it's sound design or a good idea. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] RWD Heaven: if browsers reported device capabilities in a request header

faster if the battery is more full? (For stuff like throttling down animation and XHR polling, the UA should probably prevent background tabs from draining battery even when the battery is near full regardless of whether the site/app is benevolently cooperative.) -- Henri Sivonen hsivo...@iki.fi

Re: [whatwg] RWD Heaven: if browsers reported device capabilities in a request header

of the image changing after the page load still apply, though. But still, engineering for sites varying the number of pixels they send for photos seems a bit premature when sites haven't yet adopted SVG for illustrations, diagrams, logos, icons, etc. -- Henri Sivonen hsivo...@iki.fi http

Re: [whatwg] add html-attribute for responsive images

elements that support particular functionality when node is created instead of having elements that change their nature substantially depending on attributes, network fetches, presence of plug-ins, etc., etc. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] should we add beforeload/afterload events to the web platform?

On Tue, Jan 17, 2012 at 6:29 PM, Boris Zbarsky bzbar...@mit.edu wrote: On 1/17/12 7:49 AM, Henri Sivonen wrote: On Sun, Jan 15, 2012 at 11:23 PM, Boris Zbarskybzbar...@mit.edu  wrote:  Preventing _all_ loads for a document based on some declarative thing near the start of the document

Re: [whatwg] Augmenting HTML parser to recognize new elements

than existing browsers? Have designs that don't require changes to table parsing been explored? What would be the sane way to document such changes to the HTML parser behavior? A change to the HTML spec proper *if* we decide that changes are a good idea. -- Henri Sivonen hsivo...@iki.fi http

Re: [whatwg] title/meta elements outside of head

as descendants of body is useful for Microdata and RDFa Lite without having to mint new void elements. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] should we add beforeload/afterload events to the web platform?

the majority of the web-facing use cases, we should consider adding that. So what are the Web-facing use cases? As in: What are people trying to accomplish with client-side transformations? -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] should we add beforeload/afterload events to the web platform?

threads.) -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

[whatwg] window.location aborting the parser and subsequent document.writes

. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Default encoding to UTF-8?

that be an idea? No. The current configuration works for Norwegian users already. For users from different silos, the ad might break, but ad breakage is less bad than spreading heuristic detection to more locales. Here I must disagree: Less bad for whom? For users performance-wise. -- Henri Sivonen hsivo

Re: [whatwg] Default encoding to UTF-8?

On Tue, Jan 3, 2012 at 10:33 AM, Henri Sivonen hsivo...@iki.fi wrote: A solution that would border on reasonable would be decoding as US-ASCII up to the first non-ASCII byte and then deciding between UTF-8 and the locale-specific legacy encoding by examining the first non-ASCII byte and up

Re: [whatwg] [encoding] utf-16

that Firefox could have gotten away with not having this behavior. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] [encoding] utf-16

. I'd expect Gecko to have a bug that causes it to remove *two* BOMs but not more than that. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Another bug in the HTML parsing spec?

and end tag token or a start tag token. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] document.write(\r): the spec doesn't say how to handle it.

into the tokenizer. By eager, I mean that the operation described above doesn't buffer. I.e. the first case emits an LF upon seeing a CR without waiting for an LF also to appear in the input. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Default encoding to UTF-8?

(including fall back to the encoding of the parent frame). Wouldn't that be an idea? No. The current configuration works for Norwegian users already. For users from different silos, the ad might break, but ad breakage is less bad than spreading heuristic detection to more locales. -- Henri Sivonen

Re: [whatwg] Use of media queries to limit bandwidth/data transfer

dimensions? Shouldn't those be changed to be aliases for width and height? -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] !DOCTYPE htmlbodytablemathmifoo/mi/math/table

, but not flushing out the pending table character tokens list. The reason why Gecko does what makes sense is that Gecko uses a text accumulation buffer for non-table cases, too, and any tag token flushes the buffer. (Not quite optimal for ignored tags, sure.) -- Henri Sivonen hsivo...@iki.fi http

Re: [whatwg] Default encoding to UTF-8?

On Fri, Dec 9, 2011 at 12:33 AM, Leif Halvard Silli xn--mlform-...@xn--mlform-iua.no wrote: Henri Sivonen Tue Dec 6 23:45:11 PST 2011: These localizations are nevertheless live tests. If we want to move more firmly in the direction of UTF-8, one could ask users of those 'live tests' about

Re: [whatwg] Default encoding to UTF-8?

On Tue, Dec 6, 2011 at 2:10 AM, Kornel Lesiński kor...@geekhood.net wrote: On Fri, 02 Dec 2011 15:50:31 -, Henri Sivonen hsivo...@iki.fi wrote: That compatibility mode already exists: It's the default mode--just like the quirks mode is the default for pages that don't have a doctype. You

Re: [whatwg] Default encoding to UTF-8?

to change the defaults in ways that'd break locale-siloed Existing Content. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Default encoding to UTF-8?

On Fri, Dec 2, 2011 at 6:29 PM, Glenn Maynard gl...@zewt.org wrote: On Fri, Dec 2, 2011 at 10:46 AM, Henri Sivonen hsivo...@iki.fi wrote: Regarding your (and 16) remark, considering my personal happiness at work, I'd prioritize the eradication of UTF-16 as an interchange encoding much higher

Re: [whatwg] Default encoding to UTF-8?

-dependent defaults (consider HTML in XHR). Both these efforts have faced criticism, unfortunately. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Default encoding to UTF-8?

a doctype. You opt out of the quirks mode by saying !DOCTYPE html. You opt out of the encoding compatibility mode by saying meta charset=utf-8. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] createContextualFragment in detached contexts

On Fri, Sep 30, 2011 at 7:56 PM, Erik Arvidsson a...@chromium.org wrote: On Fri, Sep 30, 2011 at 07:35, Henri Sivonen hsivo...@iki.fi wrote: On Fri, Sep 30, 2011 at 1:37 AM, Erik Arvidsson a...@chromium.org wrote: If the context object is in a detached state, then relax the parsing rules so

Re: [whatwg] Allowing custom attributes on html or body in documents for media resources

to use a style sheet with rules matching custom attributes to indicate various situations (e.g., whether the document is a toplevel browsing context) to set the viewport background. Why can't non-prefixed attributes be minted for these use cases? -- Henri Sivonen hsivo...@iki.fi http

Re: [whatwg] document.write(\r): the spec doesn't say how to handle it.

byte-order) the UTF-16-encoded byte stream into a stream of UTF-16 code units is responsible for treating unpaired surrogates as conversion errors. Sorry about not mentioning earlier that the problematic tests are also problematic in this sense. -- Henri Sivonen hsivo...@iki.fi http

Re: [whatwg] document.write(\r): the spec doesn't say how to handle it.

, what should the tokenizer do if the document.write emits half of a UTF-16 surrogate pair as the last character? The parser operates on UTF-16 code units, so a lone surrogate is emitted. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Signed XHTML

, most of the Web is HTML, so enthusiasm for XHTML-only features is likely very low these days. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] [fullscreen] Drop requestFullScreenWithKeys()?

the user do that if a mouse lock API is used also? Can a user without a pointing device do that? -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] createContextualFragment in detached contexts

way that ownerDocument.createElement would do it. I would prefer not to add a new magic mode to the parsing algorithm that'd differ from what innerHTML requires. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] input type=barcode?

) is as mainstream as Web app usage gets (banking). -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Why children of datalist elements are barred from constraint validation?

. The current design solves the problem that the datalist feature needs to Degrade Gracefully (and preferably without having to import a script library). I think the solution is quite elegant and don't see a need to drop it. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] sic element

features. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Support for RDFa in HTML5

On Tue, 2011-08-02 at 13:55 +, aykut.sen...@bild.de wrote: I would like to know if these attributes will be part of HTML5 or is there another valid method to integrate RDFa into HTML5? Why do you need RDFa? -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] date meta-tag invalid

what possessed the Google News team to use dc.date.issued instead of dc.issued or dcterms.issued. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] date meta-tag invalid

: http://wiki.whatwg.org/wiki/MetaExtensions It simply hasn't been registered yet. Is there any evidence of consuming software that does something useful with dc:created? -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Microdata feedback

. If such content abounds and non-RDF consumers are forced to support loopiness but extending the JSON conversion algorithm in ad hoc ways, part of the benefit of microdata over RDFa (treeness) is destroyed and the benefit of being well-defined would be destroyed, too, for non-RDF consumption cases. -- Henri

[whatwg] Readiness of script-created documents

that it's quite possible that Gecko followed the spec and the spec just made stuff up as opposed to the spec following Gecko.) -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

[whatwg] Linking to the HTML accessibility API mapping draft

, I imagine, isn't recommended reading in the sense of recommending that the Polyglot guide be followed for Web authoring)? -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] window.cipher HTML crypto API draft spec

. The result would not degrade gracefully. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

[whatwg] Please link to a specific fragment id on the microformats.org wiki

registrations for HTML(5) purposes. I believe changing the link to point to http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions would improve the usability of the registration procedure. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

[whatwg] DOMContentLoaded, load and current document readiness

that the same task that fires DOMContentLoaded changes the readyState to interactive and the same task that fires load changes readyState to complete? -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] CORS requests for image and video elements

? Has evangelism been attempted? -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/

Re: [whatwg] Full Screen API Feedback

was unable to find the citation for this.) Maybe you were thinking of this: http://www.bunnyhero.org/2008/05/10/scaring-people-with-fullscreen/. I'm not sure if that's the exact demo I have seen before, but it uses the same idea as the demo I've seen before. -- Henri Sivonen hsivo

  1   2   3   4   5   6   7   >