[Bug 11068] We should not pause() if the element is removed from a document and then reinserted in the same task, since otherwise that could cause stuttering when moving a video from one frame to another, and would break autoplay when used with innerHTML.
[Bug 11229] Try making an author-specific edition that has one page per section, a tree on the side, and ben's styles, as per http://www.reddit.com/r/programming/comments/dzww6/who_edits_the_w3c_specs_they_look_like_a_ransom/c14ilc2
[Bug 11279] the "assigned access key" section doesn't seem to know if it's a definition or a requirement. Should probably be rephrased to more correctly use RFC2119.
[Bug 11338] Add note saying something like "In the HTML serialization, namespace prefixes and namespace declarations are non-conforming and are do not have the same effect as in XML..."
[Bug 11343] Browsers allow *any* element to match :active between a mousedown on it and the subsequent mouseup. The definition of :active should change to match this behavior.
[Bug 11452] 4.10.22.5.5. should describe how to send the filename when the field is a file field. It should send the filename as "filename" parameter and its character encoding must be _charset_.
[Bug 11482] Requiring MIME types like application/vnd.openxmlformats-officedocument.wordprocessingml.document in order to allow a .docx file to be uploaded is far too technical for the layman. On the other hand it is equally impractical for web developers to keep an
[Bug 11505] the problem i try to solve is spam pop ups and aggressive spam page authoring (which ban you from going backward and is obviously made up for banks and exploited by spammers). my idea is to depreciate (not allow) pop ups and also the annoying backward bro
[Bug 11532] From section 6.1.5 The javascript: protocol, >When a URL using the javascript: protocol is dereferenced The "protocol" seems to be used about URI schemes with a trailing colon, but in other places schemes are referred to. All instances of "protocol" in th
[Bug 11533] clarify if specially focusable elements mean "all elements with defined valid tabindex" or "elements with a tabindex that allows sequential focusing."
[Bug 11535] tabIndex IDL default is â1 for elements that are not focusable, but if the tabindex value is negative integer, the element can still be focused.
[Bug 11592] Browsers use customizable dictionaries to correct spelling and tend to mark some names as wrong, that it shouldn't. Maybe each website can inform the browser of words/names it expects to be used and add it (in the scope of that page) to the exceptions. If
[Bug 11610] The abbr element I suggest to add the for attribute, for abbreviations and acronyms defined inline. Some solution proposals: 1. <abbr>W3C</abbr> (<title for="W3C">World Wide Web Consortium</title>) 2. <abbr>CC</abbr> (<dfn for="CC">Creative Commons</dfn>)
[Bug 11614] AAC and MP4 are ABSOLUTELY not acceptable for the open web. I don't care how many strings Apple are pulling - keep your patented encumbered trash - we don't want it.
[Bug 11626] The specification says "Time-zone offsets differ based on daylight savings time." In that case, how would you represent a time w/o date in a specific time zone? For example, how would you code "Online tech support chat hours are <time datetime="09:00:00-0
[Bug 11657] My worry is that this doesn't cover all the different kinds of textual transformations. Yes, it does cover obliqueness and weight, it does not cover letter spacing and other textual attributes that may be of some use to developers.
[Bug 11666] The value sanitisation algorithm should be clear that it sets the value property to the sanitized form. This is explicit in several cases but implicit in several cases.
[Bug 11668] Make the following note into a security warning: "It is possible that the output of this algorithm, if parsed with an HTML parser, will not return the original tree structure." and add an example of an attack (ack Eduardo Vela Nava)
[Bug 11670] "The setTransform(a, b, c, d, e, f) method must [...] invoke the transform(a, b, c, d, e, f) method" - so if I set CanvasRenderingContext2D.prototype.transform=function(){alert()}, then calling setTransform would trigger the alert? Probably this shouldn't
[Bug 11673] I need to send live data from device to URL on remote system. Would be nice to connect WebSocket, but simple access to buffer callback to package and send data to remote URL. Having access to data after closing recording interupts asynchronous processin
[Bug 11687] Make the non-normative parts of the definition of "application cache" into notes, to not mislead people into thinking they're normative. Only the list of what's in an appcache is normative here.
[Bug 11699] When calling input.focus(), should (a) the cursor be at the start, (b) the cursor be at the end or (c) the contents be selected? Please define
[Bug 11709] People evaluating this spec should be allowed to download parts of it and go through them offline, in their favorite reading device. I'm currently interested in chapters 5 and 6, but I had to go to all sorts of trouble to get those in my iPad. Please prov
[Bug 11717] [pending stable DOM Core] Element.removeAttribute() needs to lowercase its argument when used on an HTML element. (Don't add anything for removeAttributeNode.)
[Bug 11720] At the moment, chrome and opera thinks that iframe with source equal to data url has *not* the same origin as parent window's document. I think that this behavior is much more useful, because it can be used as a simpliest way of sandboxing of content.
[Bug 11746] Add video, object, img, input[type=image], embed, canvas { overflow: hidden; } since people don't expect these elements to overflow in combination with object-fit:cover (see https://bugs.webkit.org/show_bug.cgi?id=52103 )
[Bug 11748] The "size" attribute is disallowed, but may be useful on input="file". IE, Firefox and Opera all implement it, allowing you to reliably change the size of the file path textbox (Webkit browsers don't use a textbox). Styling the file upload file using CSS,
[Bug 11753] Don't like "stating what he wishes to drag and what he wishes to drop". Surely you drop what you've dragged, and the question is "where to drop it"?
[Bug 11775] Hello, I'm just writing a quick note to question the non-inclusion of the "feed" link type (rel="feed") which I remember coming across a few months ago. When I originally saw the new rel type, I was very glad to see that there was finally a way to specify
[Bug 11781] "Event handler content attributes #event-handler-content-attributes Referenced in: 7.1.1 Introduction 7.1.6.1 Event handlers (2) (3) (4), when specified, must contain valid JavaScript code matching the FunctionBody production." might be wrong since it d
[Bug 11782] The spec requires event handler content attributes to match ES5 FunctionBody, but has no similar requirement for <script> content. It probably should.
[Bug 11793] Canvas layers: have multiple drawing layers inside the canvas 2d context, right now to achieve this you must have multiple stacked canvases which isn't optimal
[Bug 11794] We should handle the case of a bunch of required controls all being hidden at once â the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation?
[Bug 11796] HTML5 SUGGESTIONS ------------------------------ This file contains suggestions of tags / features that can be added to HTML5. I sincerely hope that these features are added especially the file tag (<file></file>) which is the last I would write on. I hav
[Bug 11797] <richtext> </richtext> This will provide a default rich text widget which is scriptable and should also support the Rich Text Format (RTF) Default widget implementation should be a text area with richtext controls above it. This will enable browsers to pr
[Bug 11814] Pause on exit is not much use if the goal is to read the caption or display it using TTS since the caption has ceased to be relevant. Pause on entry might be more helpful
[Bug 11822] applet[align=bottom], embed[align=bottom], iframe[align=bottom], img[align=bottom], input[type=image][align=bottom], object[align=bottom] should not have vertical-align:baseline, but bottom
[Bug 11833] Is the logic in 'valueAsNumber' overridable? For example, if the web page wants to accept a number formatted with commas "145,000" will that be allowed?
[Bug 11861] Need to say to spin the event loop until all sync sections have run before running a new script to make resourse selection algorithm predictable. See http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-August/027878.html
[Bug 11864] section "12 IANA considerations 12.1 text/html" suggests: "This registration is for community review and will be submitted to ...registration with IANA." I understand from this that it it intended to replace RFC 2854. If so I have a problem with the stat
[Bug 11884] HAVE_ALL_DATA would be good for when the UA has finished downloading the entire media file. Also, a "loaded" or "progressend" event should be fired so users can know when a file has finished buffering.
[Bug 11900] it would be nice to specify a range for the lineWidth, eg, [1, 5], which means that the line starts at width 1, and gradually moves to width 5 at the end point
[Bug 11903] i think it'd be more convenient if explicit sections could be children of implicit sections, so you can use implicit sections in general and throw in an <aside> somewhere without breaking the outline. now if you want to throw in an <aside>, you need to ch
[Bug 11907] the event handler attributes in textTrack and TextTrackCue are marked as read only, and no other API such as addEventListener is indicated to set handlers.
[Bug 11912] HTML5 provides an opportunity to fix a long-running problem with HTTP Authentication. HTTP Authentication is important, because it is the only way to execute a request with 100% certainty that the user has provided an authentication secret. Furthermore,
[Bug 11915] Suggestion: Instead of forbidding <u> and inventing <mark> you could as well redefine <u> to be what <mark> is intended for -- roughly the same idea as for <i> and <b>. Clearly not all old HTML4 <i> / <b> / <u> match what the new HTML5 <i> / <b> / <mark>
[Bug 11926] I used new blogger template but that template very much error, i just reduce a little error html. I can't do validate at document template. Can you help me to validate new blogger template from Blogspot. Thanks.
[Bug 11930] It's very common for many application to require access to the number of video frames, as well as to have the ability to seek to a given frame. Think of a video editor. There is no notion of a video frame here. We should add fields, like "currentFrame", a
[Bug 11941] New: One of the most important features that html5 is missing in lack of 'required' attribute in select tag. While all other tags are just fine for data driven web apps, lacking of this feature in select tag really puts us to write 'extra' code for required op
[Bug 11941] One of the most important features that html5 is missing in lack of 'required' attribute in select tag. While all other tags are just fine for data driven web apps, lacking of this feature in select tag really puts us to write 'extra' code for required op
[Bug 11942] new feature suggestion: add inputmode attribute to <input> and <textarea> This already exists in XHTML Basic: http://www.w3.org/TR/2010/REC-xhtml-basic-20101123/#s_inputmode Rationale is explained in XHTML basic... Nir Dagan nir@nirdagan.com
[Bug 11942] New: new feature suggestion: add inputmode attribute to <input> and <textarea> This already exists in XHTML Basic: http://www.w3.org/TR/2010/REC-xhtml-basic-20101123/#s_inputmode Rationale is explained in XHTML basic... Nir Dagan nir@nirdagan.com
[Bug 11944] In the element "table" sub-element "thead" the example is incorrect. The "thead" and "tbody" elements are opened but no cloing tag is found.
[Bug 11944] New: In the element "table" sub-element "thead" the example is incorrect. The "thead" and "tbody" elements are opened but no cloing tag is found.
[Bug 11945] New: The table displays weirdly in WebKit -- some entries ("Z" and "m") spill over between columns, and "y" isn't aligned to the bottom. In Gecko and Opera, it doesn't display in columns at all. How about sticking with <dl> and CSS columns like in my version
[Bug 11945] The table displays weirdly in WebKit -- some entries ("Z" and "m") spill over between columns, and "y" isn't aligned to the bottom. In Gecko and Opera, it doesn't display in columns at all. How about sticking with <dl> and CSS columns like in my version
[Bug 11946] "The discarded bits mean that, for instance, atob("YQ") and atob("YR") both return "a"." was meant to be a note. Do you really want it to be normative text?
[Bug 11946] New: "The discarded bits mean that, for instance, atob("YQ") and atob("YR") both return "a"." was meant to be a note. Do you really want it to be normative text?
[Bug 11951] New: One part of this section says "Binary data with a file name" and another part says "optionally with a file name". So is it optional or not?
[Bug 11951] One part of this section says "Binary data with a file name" and another part says "optionally with a file name". So is it optional or not?
[Bug 11952] New: "the drop target has to listen to at least three events" That isn't true anymore with the dropzone attribute, right? (I know this section is non-normative...)
[Bug 11958] New: Rather than use the USB/rs232 keywords, I would recommend going with the keyword "peripheral" for any device attached to the computer. This way it would not matter if the device in question is USB, 1394, or something platform exclusive. This will future p
[Bug 11958] Rather than use the USB/rs232 keywords, I would recommend going with the keyword "peripheral" for any device attached to the computer. This way it would not matter if the device in question is USB, 1394, or something platform exclusive. This will future p
[Bug 11959] Hi, user agents are "encouraged" to make it possible to view tooltips without the use of a pointing device (it means while browsing with the keyboard for instance). Why don't we make this an obligation instead of an encouragement ? If we don't make it a "
[Bug 11959] New: Hi, user agents are "encouraged" to make it possible to view tooltips without the use of a pointing device (it means while browsing with the keyboard for instance). Why don't we make this an obligation instead of an encouragement ? If we don't make it a "
[Bug 11963] New: The namedItem(key) method must return the first node in the collection that matches the following requirements: â¢It is an a, applet, area, embed, form, frame, frameset, iframe, img, or object element with a name attribute equal to key, or, â¢It is an e
[Bug 11963] The namedItem(key) method must return the first node in the collection that matches the following requirements: â¢It is an a, applet, area, embed, form, frame, frameset, iframe, img, or object element with a name attribute equal to key, or, â¢It is an e
[Bug 11982] hi.. my name is lucy... I wonder about this new version of HTML 5.0 as HTML, if you guys can like to receive an email with all of you and tutorial information on this new version. can this be possible? my email is: luc_lawless@yahoo.com I thank you, luc
[Bug 11982] New: hi.. my name is lucy... I wonder about this new version of HTML 5.0 as HTML, if you guys can like to receive an email with all of you and tutorial information on this new version. can this be possible? my email is: luc_lawless@yahoo.com I thank you, luc
[Bug 11983] I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers.
[Bug 11983] New: I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers. I hate niggers.
[Bug 12001] New: Please enter your feedback, carefully indicating the title of the section for which you are submitting feedback, quoting the text that's wrong today if appropriate. If you're suggesting a new feature, it's really important to say what the problem you're t
[Bug 12001] Please enter your feedback, carefully indicating the title of the section for which you are submitting feedback, quoting the text that's wrong today if appropriate. If you're suggesting a new feature, it's really important to say what the problem you're t
[Bug 12002] New: User agents should provide controls to enable or disable the display of closed captions, audio description tracks, and other additional data associated with the video stream, though such features should, again, not interfere with the page's normal renderi
[Bug 12002] User agents should provide controls to enable or disable the display of closed captions, audio description tracks, and other additional data associated with the video stream, though such features should, again, not interfere with the page's normal renderi
[Bug 12005] New: It would be nice if "constructing the form data set" was an actual algorithm term and included the steps before about gathering the controls associated with the form. That way FormData(HTMLFormElement) is easier to define. And I like easy.
[Bug 12015] New: "at the time the element's "already started" flag was set" should be "at the time the element's "already started" flag was FIRST set".
[Bug 12020] New: "One byte in the range F5 to FD, followed by three bytes in the range 80 to BF, not followed by a byte in the range 80 to BF" should be "One byte in the range F8 to FD, followed by three bytes in the range 80 to BF, not followed by a byte in the range 80
[Bug 12021] Is <time>2011</time> acceptable? The formulation "precisedate" suggests that it is not, but an example says that "the year is not marked up at all, since marking it up would not be particularly useful", implying (IMHO) that it would be _possible_ to use <
[Bug 12021] New: Is <time>2011</time> acceptable? The formulation "precisedate" suggests that it is not, but an example says that "the year is not marked up at all, since marking it up would not be particularly useful", implying (IMHO) that it would be _possible_ to use <
[Bug 12023] New: How shall invalid code points from U+D800 to U+DFFF be handled - a replacement character U+FFFD REPLACEMENT CHARACTER for each byte or the whole sequence (I assume the latter)
[Bug 12024] New: Should make it clear that when an <object> navigates to a resource given in its data="" attribute, the fetching is done by the <object>'s algorithm and _not_ the "navigate" algorithm. In particular, there's a note in the <object> section about appcaches m
[Bug 12041] New: Probably this should be: "Labeling a resource with the application/microdata+json type asserts that the resource is a JSON text that consists of an object with a single entry called "items" consisting of an array of entries, each of which consists of an o
[Bug 12044] New: This is a new feature request. Request overview: Give developers an option to disable a context's image smoothing (ie, anti-assailing). Problem: When scaling up images, most user agents smooth the output. This is fine for most use cases, but is undesirabl
[Bug 12061] New: step 3 says to "set the node to the context element", but I do not see "context element" defined anywhere. Should that be the "current node" or perhaps "current table"?
[Bug 12061] step 3 says to "set the node to the context element", but I do not see "context element" defined anywhere. Should that be the "current node" or perhaps "current table"?
[Bug 12065] New: Please point out that for <input type=file multiple> http://tools.ietf.org/html/rfc2388#section-4.2 should not be used. Instead each file should have its own field. Otherwise you break PHP.
[Bug 12065] Please point out that for <input type=file multiple> http://tools.ietf.org/html/rfc2388#section-4.2 should not be used. Instead each file should have its own field. Otherwise you break PHP.
[Bug 12085] New: Please drop "The following features are defined in the DOM Range specification: [DOMRANGE]" and the following list; only Selection used those terms
[Bug 12085] Please drop "The following features are defined in the DOM Range specification: [DOMRANGE]" and the following list; only Selection used those terms
[Bug 12088] New: Under 4.8.11.1.2, Transformations, the specification reads: The transformations must be performed in reverse order. For instance, if a scale transformation that doubles the width is applied, followed by a rotation transformation that rotates drawing opera
[Bug 12088] Under 4.8.11.1.2, Transformations, the specification reads: The transformations must be performed in reverse order. For instance, if a scale transformation that doubles the width is applied, followed by a rotation transformation that rotates drawing opera
[Bug 12089] New: Under 4.8.11.1.2, Transformations, the specification reads: The transformations must be performed in reverse order. For instance, if a scale transformation that doubles the width is applied, followed by a rotation transformation that rotates drawing opera
[Bug 12089] Under 4.8.11.1.2, Transformations, the specification reads: The transformations must be performed in reverse order. For instance, if a scale transformation that doubles the width is applied, followed by a rotation transformation that rotates drawing opera
[Bug 12095] <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <!-- saved from url=(0023)http://officena.com/ib/ --> </STYLE><!-- // please keep these lines on when you copy the source // made by: Nicolas - http://www.javascript-page.com var mymessage = "
[Bug 12095] New: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <!-- saved from url=(0023)http://officena.com/ib/ --> </STYLE><!-- // please keep these lines on when you copy the source // made by: Nicolas - http://www.javascript-page.com var mymessage = "
[Bug 12100] New: UAs do not actually convert DOMStrings to sequences of Unicode characters. Test case: data:text/html,<!doctype html><script>document.documentElement.title = "\ud800"; alert(document.documentElement.title.charCodeAt(0));</script> Expected 65533, got 5529
[Bug 12100] UAs do not actually convert DOMStrings to sequences of Unicode characters. Test case: data:text/html,<!doctype html><script>document.documentElement.title = "\ud800"; alert(document.documentElement.title.charCodeAt(0));</script> Expected 65533, got 5529
[Bug 12101] New: "Structured clone" can be passed an object with a hostile getter that returns an object identical to itself; "structured clone" does not prevent such an infinite regression.
[Bug 12103] New: currently no browser supports seamless attribute on iframes, frameborder and scrolling should not cause validation errors in HTML5. They should be allowed but not recommended possibly.
[Bug 12106] 1. <quote> <!DOCTYPE HTML> </quote> Is this declaration part of an html document? Or is this part of a Document Type Definition (DTD)? Where are DTDs for html documents defined? 2. <title> Resource metadata management </title> <quote> A Document is always
[Bug 12106] New: 1. <quote> <!DOCTYPE HTML> </quote> Is this declaration part of an html document? Or is this part of a Document Type Definition (DTD)? Where are DTDs for html documents defined? 2. <title> Resource metadata management </title> <quote> A Document is always
[Bug 12110] New: The margin note shows no support but at least IE 8 and Firefox 3.6 support dropzone=link for an image. So does Chrome 9, which also supports dropzone=move (when the origin has editable content).
[Bug 12119] New: This section is not clear about how to make a progress element transition from determinate to indeterminate. As written, it sounds as if I'd have to call removeAttribute('value') to make it go into indeterminate mode. But I suspect that the intent is th
[Bug 12119] This section is not clear about how to make a progress element transition from determinate to indeterminate. As written, it sounds as if I'd have to call removeAttribute('value') to make it go into indeterminate mode. But I suspect that the intent is th
[Bug 12147] New: It's not "little green guys with guns", it's "diminutively-sized colorfully challenged persons expressing their second amendment rights".
[Bug 12148] I strongly believe disallowing 'true' and 'false' in boolean attributes will cause significant confusion in the future. Already, you can find respected web developers incorrectly referring to attributes as true and false. For instance: http://blog.getif
[Bug 12148] New: I strongly believe disallowing 'true' and 'false' in boolean attributes will cause significant confusion in the future. Already, you can find respected web developers incorrectly referring to attributes as true and false. For instance: http://blog.getif
[Bug 12149] New: The argument name is "scheme", but you call it "protocol" in this text: The arguments to the methods have the following meanings and corresponding implementation requirements: protocol (registerProtocolHandler() only)
[Bug 12149] The argument name is "scheme", but you call it "protocol" in this text: The arguments to the methods have the following meanings and corresponding implementation requirements: protocol (registerProtocolHandler() only)
[Bug 12152] New: Charset attribute is (in HTML 4) supposed to inform the browser beforehand about the encoding (before making an HTTP request), and it may also be useful if the resource is not transferred via HTTP or it is sent without suitable Content-Type header. The cu
[Bug 12154] b and strong should be font-weight: bolder, not font-weight: bold. IE9 RC, Firefox 4b11, and WebKit all agree, with only Opera differing. Test case: data:text/html,<!doctype html><p style=font-weight:100><b>Should be bold per current spec</b>
[Bug 12154] New: b and strong should be font-weight: bolder, not font-weight: bold. IE9 RC, Firefox 4b11, and WebKit all agree, with only Opera differing. Test case: data:text/html,<!doctype html><p style=font-weight:100><b>Should be bold per current spec</b>
[Bug 12162] New: Overall comment. A downloadable PDF of the altest editor's draft would be a useful way for readers to access the spec. Personally I would like to add my own comments and notations as I read the sepc, but this is only possible with a PDF. I tried creating
[Bug 12163] New: The illustration of header associations for the ID/Measurement/Average/Maximum table is incorrect. Since the header cells "Legs" and "Tails" (in both rowgroups) do not have scope attributes set to "row" and they have data cells to their left, they are not
[Bug 12164] New: People, are you crazy?! Why are you putting the entire spec into a single file?? It takes forever to load, and locks up the browser in the process. Split it up and use hyperlinks, like the rest of the world!
[Bug 12164] People, are you crazy?! Why are you putting the entire spec into a single file?? It takes forever to load, and locks up the browser in the process. Split it up and use hyperlinks, like the rest of the world!
[Bug 12165] New: The requirement on the plaintext element conflicts with its old definition and usage. It is better to avoid requiring any support than to require support that breaks legacy usage. The plaintext element should be regarded as undefined in HTML5.
[Bug 12165] The requirement on the plaintext element conflicts with its old definition and usage. It is better to avoid requiring any support than to require support that breaks legacy usage. The plaintext element should be regarded as undefined in HTML5.
[Bug 12166] New: The requirement on the xmp element conflicts with its old definition (which requires a special parsing mode where no markup except the element's end tag is recognized) and usage. It is better to avoid requiring any support than to require support that bre
[Bug 12166] The requirement on the xmp element conflicts with its old definition (which requires a special parsing mode where no markup except the element's end tag is recognized) and usage. It is better to avoid requiring any support than to require support that bre
[Bug 12167] New: The requirement on the listing element conflicts with its old definition (which requires a special parsing mode where no markup except the element's end tag is recognized) and usage. It is better to avoid requiring any support than to require support that
[Bug 12167] The requirement on the listing element conflicts with its old definition (which requires a special parsing mode where no markup except the element's end tag is recognized) and usage. It is better to avoid requiring any support than to require support that
[Bug 12171] Define "resolve an address" here until there's a useful spec to reference. The lack of specification seriously hurts any attempt to improve interoperability for anything related to URLs
[Bug 12171] New: Define "resolve an address" here until there's a useful spec to reference. The lack of specification seriously hurts any attempt to improve interoperability for anything related to URLs
[Bug 12181] New: The text in 4.12.4.17.1 conflicts with existing practice, older (e.g. HTML 4) descriptions, and the brief summary in the table at the start of 4.12.4, where "index" is described thusly: "Gives a link to the document that provides a table of contents or in
[Bug 12186] New: Should explicitly state that TimeRanges.end() is inclusive, so that if the browser reverts to HAVE_METADATA while playing, the .buffered.end(0) value is the last rendered frame, and .currentTime is the next frame, and so that when .ended is true, .buffere
[Bug 12186] Should explicitly state that TimeRanges.end() is inclusive, so that if the browser reverts to HAVE_METADATA while playing, the .buffered.end(0) value is the last rendered frame, and .currentTime is the next frame, and so that when .ended is true, .buffere
[Bug 12191] New: The spec doesn't currently seem to handle the situation of seeking to a point beyond the end of a presumed-infinite stream, whether by advancing monotonically to that point or arbitrarily seeking to that point.
[Bug 12191] The spec doesn't currently seem to handle the situation of seeking to a point beyond the end of a presumed-infinite stream, whether by advancing monotonically to that point or arbitrarily seeking to that point.
[Bug 12193] It would be nice to hide the html5(html+css+js) code.The visibility of the code makes it vulnerable to certain types of hacks and ofcourse proprietary code which the developer might wish not to share.please consider this request
[Bug 12193] New: It would be nice to hide the html5(html+css+js) code.The visibility of the code makes it vulnerable to certain types of hacks and ofcourse proprietary code which the developer might wish not to share.please consider this request
[Bug 12199] New: Step 4.4 "For each character ..." -> It must operate on a sequence of characters, not on a character. Otherwise it would generate overlong form when the encoding is stateful (e.g. consider ISO-2022-JP's escape sequences).
[Bug 12203] Inconsistent capitalization of "Windows". IANA 1252 uses lowercase, IANA 1254 uses uppercase, so ignore offical versions and go with what makes sense, which is "Windows"
[Bug 12203] New: Inconsistent capitalization of "Windows". IANA 1252 uses lowercase, IANA 1254 uses uppercase, so ignore offical versions and go with what makes sense, which is "Windows"
[Bug 12204] Inconsistent capitalization of "Windows". IANA 1252 uses lowercase, IANA 1254 uses uppercase, so ignore offical versions and go with what makes sense, which is "Windows"
[Bug 12204] New: Inconsistent capitalization of "Windows". IANA 1252 uses lowercase, IANA 1254 uses uppercase, so ignore offical versions and go with what makes sense, which is "Windows"
applet obsoleted It seems that the committee is being deliberately hostile to Java applets. This is based on the fact that, with the proposed change, it will no longer be possible to include an applet in such a way as to be compatible with all browse