[whatwg] Security: emphasize that subdomain is not enough for user provided scriptable content

The page https://html.spec.whatwg.org/dev/iframe-embed-object.html contains an example that has "usercontent.example.net" instead of e.g. "video.example.com" used in the same chapter. It does have a warning saying It is important to use a separate domain so that if the attacker convinces t

[whatwg] rendering for case min == max

According to https://html.spec.whatwg.org/multipage/form-elements.html#the-meter-element following inequalities must hold for : minimum ≤ value ≤ maximum minimum ≤ low ≤ maximum (if low is specified) minimum ≤ high ≤ maximum (if high is specified) minimum ≤ optimum ≤ maximum (if optimum is

Re: [whatwg] Adding progress event for native ?

Anne van Kesteren (2017-04-12 10:25 Europe/Helsinki): > On Wed, Apr 12, 2017 at 9:16 AM, Mikko Rantalainen > wrote: >> The default use case would not need to use frames. The expected use case >> would be to display custom UI for submission progress (e.g. nice >> progress

Re: [whatwg] Adding progress event for native ?

Anne van Kesteren (2017-04-11 16:05 Europe/Helsinki): > On Tue, Apr 11, 2017 at 2:44 PM, Mikko Rantalainen > wrote: >> Would it be possible to add "progress", "load", etc. events to normal >> form elements, too? Basically, I would like to do >> >&g

[whatwg] Adding progress event for native ?

I see that https://xhr.spec.whatwg.org/ already defines ProgressEvent for XMLHttpRequest. Would it be possible to add "progress", "load", etc. events to normal form elements, too? Basically, I would like to do form.addEventListener('progress', function (e) {...}) and if the end user hits the S

[whatwg] Document with a single input[type=radio]?

The spec says in 4.10.5.1.16 Radio Button state (type=radio) https://html.spec.whatwg.org/multipage/forms.html#radio-button-state-%28type=radio%29 "A document must not contain an input element whose radio button group contains only that element." What this is supposed to mean in practice? Could

Re: [whatwg] Parsing: how to deal with marker while reconstructing the active formatting elements?

Simon Pieters (2015-04-08 11:07 Europe/Helsinki): On Wed, 08 Apr 2015 07:55:26 +0200, Mikko Rantalainen wrote: The section 12.2.3.3 The list of active formatting elements (https://html.spec.whatwg.org/multipage/syntax.html#the-list-of-active-formatting-elements) has steps to "reconstruc

[whatwg] Parsing: how to deal with marker while reconstructing the active formatting elements?

The section 12.2.3.3 The list of active formatting elements (https://html.spec.whatwg.org/multipage/syntax.html#the-list-of-active-formatting-elements) has steps to "reconstruct the active formatting elements". The steps include Step 6: "If entry is neither a marker nor an element that is also

[whatwg] Improving ?

The element currently supports only 3 possible values for @preload attribute [1]. Real world user agent implementations agree on keyword "none" only. Both "metadata" and "auto" have a pretty poor interoperability, especially considering the amount of actual data transferred if user never hits

Re: [whatwg] Proposal: Specify SHA512 hash of JavaScript files in

Sorry for the late response. Igor Minar, 2014-02-05 03:08 (Europe/Helsinki): I've been in discussions in the past where developers expressed concerns about inability to verify that the bits delivered from CDN were the same bits as the ones they reviewed and tested against during development. It

Re: [whatwg] canvas 2d's ellipse

Rik Cabanier, 2013-09-18 00:32 (Europe/Helsinki): You are speaking as a developer, not as a user of a web application. Browser could offer a 'debug' more where they break on bad calls or output messages to the console. Once it's 'released', the runtime should be permissive. I somewhat agree. Ho

Re: [whatwg] Add "Switch" Type

Brian M. Blakely, 2013-09-21 02:03 (Europe/Helsinki): I was contemplating whether to propose a new input type, or an attribute valid only for checkboxes. But it isn't a checkbox, so I went with a new type value. You can choose to slide the switch or click it in most OS implementations, so even t

Re: [whatwg] Proposal: Adding methods like getElementById and getElementsByTagName to DocumentFragments

Boris Zbarsky, 2013-07-03 17:50 (Europe/Helsinki): On 7/3/13 3:58 AM, Mikko Rantalainen wrote: Boris Zbarsky, 2013-06-29 05:02 (Europe/Helsinki): On 6/28/13 6:51 PM, Tab Atkins Jr. wrote: querySelector is simply a more powerful querying function than the old DOM methods, And somewhat slower

Re: [whatwg] Proposal: Adding methods like getElementById and getElementsByTagName to DocumentFragments

Boris Zbarsky, 2013-06-29 05:02 (Europe/Helsinki): On 6/28/13 6:51 PM, Tab Atkins Jr. wrote: querySelector is simply a more powerful querying function than the old DOM methods, And somewhat slower as a result, note. If that's true, I would consider that as a bug. It should be really simple

Re: [whatwg] Is now an official HTML5 element?

Ian Yang, 2013-02-14 03:21 (Europe/Helsinki): > > lorem ipsum > > ... > > > ... > > > ... > I find the logic to be that if you use and/or you should wrap the main content within . Then use and for the structure. One thing worth noting is that unlike id="main" or role="main", the

Re: [whatwg] Registration points for elements

Ian Hickson, 2013-01-08 18:23 (Europe/Helsinki): > You can do this with anything in HTML, using absolute positioning: set > just one of the coordinates in each direction, and leave the other on > 'auto'. As in: > >div { position: absolute: bottom: 10em; right: 10em; width: auto; > h

Re: [whatwg] Fwd: fallback section taking over for 4xx and 5xx responses while online

Ian Hickson, 2012-12-17 23:30 (Europe/Helsinki): > On Tue, 11 Dec 2012, David Barrett-Kahn wrote: >> browser that the response is not to trigger the fallback entry, despite >> its response code. Something like it could be considered for > > Can you elaborate on the need for this feature? Why wo

Re: [whatwg] Making cross-origin (partly) usable

Ian Hickson, 2012-12-01 04:57 (Europe/Helsinki): > ...and Adam Barth posted some on the wiki: >> Expandable Advertisement: A publisher wishes to display an advertisement >> that expands when the user interacts with the advertisement. Today, the >> common practice is for the advertising network to

Re: [whatwg] 'datetime-local' and 'datetime' comments

Mikko Rantalainen, 2012-11-27 10:18 (Europe/Helsinki): > (3) Timezones are subject to future political decisions If you think this is a real problem, see http://www.timeanddate.com/news/time/ for examples. Current examples from the top of the page: 26-Oct-2012 Russia remains on summer t

Re: [whatwg] 'datetime-local' and 'datetime' comments

Nicolas Froidure, 2012-11-13 12:51 (Europe/Helsinki): > In my opinion, it's normal that datetime and datetime-local have > timezone and date/time don't. A date is timezone independant and time is > more a duration then a time relative to a particular instant of a > particular day. Unfortunately, "

Re: [whatwg] 'datetime-local' and 'datetime' comments

Ian Hickson, 2012-11-22 07:15 (Europe/Helsinki): > On Wed, 21 Nov 2012, Mounir Lamouri wrote: >> Then, maybe a better naming could be "datetime-utc"? > > I think that would mislead authors into thinking that the UI that users > will see is one that asks for a UTC time. That kind of UI is the wors

Re: [whatwg] URL: file: URLs

João Eiras, 2012-10-31 01:41 (Europe/Helsinki): > In both Firefox and Chrome if you type file://aaa/some/path, or > file://localhost/some/path, the aaa and localhost parts are ignored, and > the rest of the path is interpreted as a local file path. In Opera, > anything that is not localhost gives a

Re: [whatwg] Real-time thread support for workers

Ian Hickson, 2012-10-27 03:14 (Europe/Helsinki): > On Thu, 9 Aug 2012, Jussi Kalliokoski wrote: >> >> On W3C AudioWG we're currently discussing the possibility of having web >> workers that run in a priority/RT thread. This would be highly useful >> for example to keep audio from glitching even u

Re: [whatwg] checksum attribute in a href tag

Ian Hickson, 2012-10-24 19:28 (Europe/Helsinki): > Anyway, if you have memory corruption there's nothing to say the > corruption won't occur _after_ you've done the checksum verification. In > particular, there's nothing to say it'll happen between receiving and > decoding the packets over TLS a

Re: [whatwg] checksum attribute in a href tag

Anne van Kesteren, 2012-10-19 14:57 (Europe/Helsinki): > On Fri, Oct 19, 2012 at 1:50 PM, A. Rauschenbach > wrote: >> I'm sick of coping the checksum of important files by hand or QR-code to the >> download manager or console. >> >> To solve the problem I suggest a checksum attribute in the tag.

Re: [whatwg] Submitting contentEditable Content In A Form

2012-09-07 11:57 Europe/Helsinki: Hugh Guiney: > JavaScript into, say, a hidden form field. I think that there should > be some mechanism to associate contentEditable elements with > forms—maybe the combination of contentEditable="true" and the presence > of @name creates an implicit form control?

Re: [whatwg] input type=barcode?

2012-09-07 07:35 Europe/Helsinki: Ian Hickson: > On Thu, 30 Aug 2012, Jonas Sicking wrote: >> >> I think while in theory we could rely on UAs to enable barcode entry >> anywhere, which definitely would provide the maximum capabilities for > [...] > > In this respect it's similar to the WebKit-p

Re: [whatwg] responsive images

2012-05-22 13:53 Europe/Helsinki: Paul Court: > > > Not to mention, what happens when a 3x device is released? Do I have > to change all my code again? As I see it, there's no way around it. And the important point to notice is that this fact does not depend on the syntax. Also notice that it w

Re: [whatwg] Throwing in my support for into the mix

2012-05-16 18:01 Europe/Helsinki: Julian Reschke: > On 2012-05-16 16:36, Glenn Maynard wrote: >> On Wed, May 16, 2012 at 9:16 AM, Julian Reschke > > wrote: >> Actually, the key point is that this is non-conforming to start >> with: image candidate strings must have at

Re: [whatwg] Features for responsive Web design

2012-05-16 10:19 Europe/Helsinki: Tab Atkins Jr.: > On Wed, May 16, 2012 at 12:14 AM, Mikko Rantalainen > wrote: >> I think that the correct syntax would be >> >> >> >> because the author assumes that the image will be rendered as 300x150. > > No, th

Re: [whatwg] Features for responsive Web design

2012-05-16 03:26 Europe/Helsinki: Tab Atkins Jr.: > On Tue, May 15, 2012 at 5:15 PM, Jason Grigsby wrote: >> In the @srcset syntax, I *think* I would end up with something like this: >> >> > srcset="a-rectangle.png 300w 150h 1x, >> a-square.png 100w 100h 1x"> > > Nope, what you wa

Re: [whatwg] Signed XHTML

2011-10-27 14:29 EEST: Henri Sivonen: > On Thu, Oct 20, 2011 at 9:57 PM, Martin Boßlet > wrote: >> Are there plans in this direction? Would functionality like this have a >> chance to be considered for the standard? > > The chances are extremely slim. > > XML signatures depend on XML canonicaliz

Re: [whatwg] Fullscreen Update

2011-10-19 17:45 EEST: Glenn Maynard: > b.onclick = function(e) { > if(document.fullscreen) > document.exitFullscreen(); > else > gameDiv.enterFullScreen(); > } In fact, the most obvious code should be b.onclick = function(e) { if(gameDiv.fullscreen) gameDiv.ex

Re: [whatwg] Proposal for improved handling of '#' inside of data URIs

2011-09-11 00:15 EEST: Daniel Holbert: > Browsers handle the "#" character in data URIs very differently, and the > arguably "correct" behavior is probably not what authors actually want > in many cases. > > This could be more intuitive/do-what-I-mean if we restricted the cases > under which "#" i

[whatwg] input type=barcode?

Use case: A form author expects user to enter some kind of code (e.g. driver id number, bank transfer code, product serial for warranty etc.) that is accompanied with a barcode on paper. The end user finds it hard to manually type the code. Possible solution: The form could hint the user agent a

Re: [whatwg] Support for page transitions

2011-06-07 18:07 EEST: Bjartur Thorlacius: > On 6/7/11, Mikko Rantalainen wrote:> >> Note that the "next page" button may or may not match with rel="next" >> and as such, I think that there should be additional method for > Elaborate; they both re

Re: [whatwg] Support for page transitions

2011-06-08 01:37 EEST: Aryeh Gregor: > On Tue, Jun 7, 2011 at 7:45 AM, Mikko Rantalainen > wrote: >> The things I don't want to have in this specification (page author control): >> >> - actual transition animation ("slide the next page from the left") &

[whatwg] Support for page transitions

I'm pretty sure that most people on this list have seen page transitions in Internet Explorer 5.5+ (http://msdn.microsoft.com/en-us/library/ms532847%28v=vs.85%29.aspx#Interpage_Transition). I think that web application user experience could be improved if transitions between pages were supported.

Re: [whatwg] Can we deprecate alert(), confirm(), prompt() ?

2011-03-01 11:13 EEST: Robert O'Callahan: > On Tue, Mar 1, 2011 at 6:38 PM, Ojan Vafai wrote: > >> FWIW, chromium is planning on experimenting with disallowing modal dialogs >> during the beforeunload/unload events. >> http://code.google.com/p/chromium/issues/detail?id=68780 > > That sounds fair

Re: [whatwg] Limiting the amount of downloaded but not watched video

2011-01-18 23:37 EEST: Glenn Maynard: > On Tue, Jan 18, 2011 at 8:40 AM, Boris Zbarsky wrote: >> On 1/18/11 6:09 AM, Glenn Maynard wrote: >> >>> I'm confused--how is the required buffer size a function of the length of >>> the video? Once the buffer is large enough to smooth out network >>> fluct

Re: [whatwg] Limiting the amount of downloaded but not watched video

2011-01-17 23:32 EEST: Silvia Pfeiffer: > On Mon, Jan 17, 2011 at 10:15 PM, Chris Pearce wrote: >> Perhaps we should only honour the downloadBufferTarget (or whatever measure >> we use) when the media is in readyState HAVE_ENOUGH_DATA, i.e. if we're >> downloading at a rate greater than what we re

Re: [whatwg] Make radio button group suffering from being missing

2011-01-08 00:06 EEST: Ian Hickson: > The basic idea behind this design is that type=radio seems to have been > designed to keep each control as independent as possible -- before we > started fiddling with it in WF2, the only way type=radio controls had any > relationship to other type=radio con

Re: [whatwg] HTML5 video: frame accuracy / SMPTE

2011-01-12 00:40 EEST: Rob Coenen: > Hi David- that is b/c in an ideal world I'd want to seek to a time expressed > as a SMPTE timecode (think web apps that let users step x frames back, seek > y frames forward etc.). In order to convert SMPTE to the floating point > value for video.seekTime I need

Re: [whatwg] Proposal for secure key-value data stores

2010-12-01 21:43 EEST: Aryeh Gregor: > On Tue, Nov 30, 2010 at 6:15 PM, Ian Hickson wrote: >> It cannot, and should not. It's a user concern. If as a user I want all >> data that you send me to be printed unencrypted and dropped out of my >> office window for anyone to read, then I should be allow

Re: [whatwg] Improve select required

2010-11-16 04:16 EEST: Ian Hickson: > On Thu, 12 Aug 2010, Mikko Rantalainen wrote: >> A possible use case where this feature could be useful already (and >> cannot be fulfilled with @required): >> >> 1) An user is trying to register a new user account on some system

Re: [whatwg] Scriptable interface for video element FullScreen mode

2010-09-23 06:26 EEST: Shiv Kumar: >> Is this proposal not good enough? >> https://wiki.mozilla.org/index.php?title=Gecko:FullScreenAPI > > That proposal covers the video element but is way too broad. Digesting and > analyzing it would take quite an effort. It will probably also require a > really

Re: [whatwg] Video with MIME type application/octet-stream

2010-09-13 16:44 EEST: Roger Hågensen: > On 2010-09-13 15:03, Mikko Rantalainen wrote: >> And why do we need this? Because web servers are not behaving correctly >> and are sending incorrect Content-Type headers? What makes you believe >> that BINID will not be incorrectly

Re: [whatwg] Video with MIME type application/octet-stream

2010-09-11 01:51 EEST: Roger Hågensen: > On 2010-09-09 09:24, Philip Jägenstedt wrote: >> For at least WAVE, Ogg and WebM it's not possible as they begin with >> different magic bytes. > > Then why not define a new "magic" that is universal, so that if a proper > content type is not stated then a

Re: [whatwg] select element should have a required attribute

2010-08-11 12:31 EEST: Jonas Sicking: > On Wed, Aug 11, 2010 at 2:03 AM, Mikko Rantalainen > wrote: >> Stuff I don't want to see (combined with @required): >> >> - first option is always special >> - empty string as the value is special >> - option withou

Re: [whatwg] select element should have a required attribute

2010-08-10 21:25 EEST: Tab Atkins Jr.: > On Tue, Aug 10, 2010 at 11:12 AM, Mike Wilcox wrote: >> This seems like the ideal situation to use a placeholder attribute: >> >> >> Foo >> Bar >> None >> > > Almost, but not quite. > > Yes, the value used in this situation is essentially

Re: [whatwg] input type=ink proposal

2010-06-08 19:26 EEST: Charles Pritchard: > Has there been prior discussion about an input type="ink" form element? > > This element would simply capture coordinates from a mouse (or touch/pen > input device), > allowing the user to reset the value of the element at their discretion. > > InkML is

Re: [whatwg] More YouTube response

2010-07-05 01:56 EEST: David Gerard: On 4 July 2010 13:57, bjartur wrote: I fail to see how BBC would be harmed by the usage of alternative software. Its business model is about content, not software, right? See, you're using logic and sense ... about half the BBC want to just *make their st

Re: [whatwg] meta="encrypt" tag is needed

Juuso Hukkanen wrote: > Mikko Rantalainen wrote: >> Are you trying to suggest an user agent implementation of something >> similar to this: http://angel.net/~nic/passwdlet.html ? > Thanks Mikko for linking to those passsalt generator tools. In truth, I was asking to figure

Re: [whatwg] meta="encrypt" tag is needed

Juuso Hukkanen wrote: > I was expecting criticism; as is unavoidable with all crypto issues. > > You asked many questions, and unfortunately all you missed the > auth="verisign" argument, which _is_ enough to prevent all practical > (,even if they are all theoretical!,) man-in-the-middle attacks.

Re: [whatwg] Changing punctuation value of input element in telephone state

Ashley Sheridan wrote: > On Wed, 2010-04-07 at 01:28 +0200, Eduard Pascual wrote: > >> On Wed, Apr 7, 2010 at 1:10 AM, Ian Hickson wrote: >>> If there was a true standard, then the spec would refer to that, but as >>> you say, it's very varied in practice. >> There is quite a standard, even if an

Re: [whatwg] Structured clone algorithm a little too friendly?

timeless wrote: > On Tue, Mar 2, 2010 at 12:50 AM, ben turner wrote: >> - If input is a host object (e.g. a DOM node) >> Return the null value. > > The general reason, I believe for this behavior is if you have: > > a=[x,y,z,q,r,s]; worker.postMessage(a) and r turns out to be window, > you

Re: [whatwg] Video source selection based on quality

David Singer wrote: > I am by no means convinced that automatic selection of sources other > than that based on the most obvious, automated, criteria, is wise or > needed. We have had for many years, in QuickTime, this facility, and > quite a few sites opted not to use it and allow the user a manu

Re: [whatwg] Codecs for and

Ian Hickson wrote: > on the situation regarding codecs for and in HTML5, I have > reluctantly come to the conclusion that there is no suitable codec that > all vendors are willing to implement and ship. > > I have therefore removed the two subsections in the HTML5 spec in which > codecs would

Re: [whatwg] New work on fonts at W3C

Aryeh Gregor wrote: > On Mon, Jun 22, 2009 at 10:43 AM, Brad Kemper wrote: >> This makes sense to me. I was surprised and found it counter-intuitive to >> learn that CORS could be used to list the servers that are allowed access, >> but could not and would not restrict access to servers not on that

Re: [whatwg] New work on fonts at W3C

Anne van Kesteren wrote: > On Sat, 20 Jun 2009 17:07:06 +0200, Brad Kemper > wrote: >> I didn't mean it should be restricted by default. Just that CORS could >> restrict it like anything else if you told it to. And that the font >> could instruct the CORS mechanism. > > That's not how CORS works.

Re: [whatwg]

Tom Duhamel wrote: > that the use of non Gregorian is to be supported, I would go with the later > solution (allow non Gregorian as the content only, and have the datetime > attribute always defined as a Gregorian date), since that would not put much How about specifying that the content of eleme

Re: [whatwg]

Smylers wrote: > Robert J Burns writes: >> Right now we have a draft that: 2) allows without attaching >> sufficient meaning to it > > I don't think that's the case; the algorithm for parsing a year requires > a number "greater than zero": > > > http://www.whatwg.org/specs/web-apps/curren

Re: [whatwg]

Leif Halvard Silli wrote: > Mikko Rantalainen 2009-03-13 11.33: >> Andy Mabbett wrote: >>> In message , >>> Jim O'Donnell writes > And is also touted as an accessibilty feature. And this > Proleptic Gregorian calendar is, I hear, supposed to - >

Re: [whatwg]

Andy Mabbett wrote: > In message , > Jim O'Donnell writes > >> This is already a solved problem in the Text Encoding Intiative (TEI). >> The value of a date/time is encoded in the Gregorian calendar, using >> ISO8601. The calendar attribute is used to indicate the calendar of >> the origin

Re: [whatwg] Spellchecking mark III

James Graham wrote: > Mikko Rantalainen wrote: >> My second sentence was trying to argument that page author has no >> business forcing the spellchecking on if the page author cannot force >> the spellchecking language! Especially for a case where the page >> contains

Re: [whatwg] Spellchecking mark III

Peter Kasting wrote: > 2009/1/20 Mikko Rantalainen > >> I agree. I think that specifying the spellcheck attribute would be a >> mistake. It allows only forcing the automatic spell checking on or off >> but it doesn't help a bit to allow mixing different language

Re: [whatwg] Spellchecking mark III

Křištof Želechovski wrote: > Spell checking of regions of text should be governed by the lang attribute, > if any, and browser preferences; it would be switched off for language tags > the spell-checking engine does not support, including custom ones. > It is extremely annoying how Safari, although

Re: [whatwg] native styling for search input boxes

Nils Dagsson Moskopp wrote: > the look of the input field could be styled just by a value of "search" > for the CSS "appearance". that would have to go through CSS3 WG, but > would probabvy be the cleanest approach. > > http://www.w3.org/TR/css3-ui/#system See also: http://lipidity.com/apple/ipho

Re: [whatwg] Scripted querying of capabilities

Tim Starling wrote: > Henri Sivonen wrote: >> On Aug 7, 2008, at 09:53, Tim Starling wrote: >> >>>xiphQtVersion = videoElt.GetComponentVersion('imdc','XiTh', >>> 'Xiph'); >> >> This kind of FourCC use is exactly the kind of thing I meant earlier >> when I asked if the MIME stuff is really t

Re: [whatwg] Sandboxing to accommodate user generated content.

Frode Børli wrote: >>> I have been reading up on past discussions on sandboxing content, and >>> >>> My main arguments for having this feature (in one form or another) in >>> the browser is: >>> >>> - It is future proof. Changes to browsers (for example adding >>> expression support to css) will ne

Re: [whatwg] Thoughts on HTML 5 - dialog

Ian Hickson wrote: > On Tue, 13 May 2008, Ernest Cline wrote: > I agree that isn't perfect and could be (and has been) confused > with dialog boxes, but I'm not convinced it's not the best name for the > job anyway. > >> The other possibility is since the computing uses that cause >> confusio

Re: [whatwg] several messages about proposals

Ian Hickson wrote: > On Tue, 24 Apr 2007, Elliotte Harold wrote: >> It occurs to me that one of the most frequently used nits of >> pseudo-markup is to indicate sarcasm. For example, >> >> Yeah, George W. Bush has been such a great president. >> >> Should we perhaps formalize this? Is there any be

Re: [whatwg] less than normal importance/emphasis (was: several messages about and many related subjects)

latter markup represents that there're two separate important parts in that paragraph. I think there should be exactly one important part and one less important part. > On Fri, 9 Feb 2007, Mikko Rantalainen wrote: >> I believe that and are different from de-emphasis (that >> woul

Re: [whatwg] Calendar subscription as a feed?

Dan Mosedale wrote: > Dan Mosedale wrote: >> One nice property of the webcal: URI scheme is that any user-agent can >> reasonably infer the intended use (which is likely to carry the >> semantic that the URI will be around for a longer period of time) >> simply from the URI. So this URI can si

[whatwg] Calendar subscription as a feed?

Consider a site that has something like an event calendar (may be displayed with a table layout or just a simple list). How should one link to iCalendar information that is meant for subscription or importing to reader's calendaring software? (This is different from a single event information for w

Re: [whatwg] accesskey

Matthew Paul Thomas wrote: > Michael(tm) Smith wrote: >> Jerason Banes <[EMAIL PROTECTED]>, 2008-01-25 23:41 -0600: >> >>> Long story short, accesskeys were an idea that worked better on paper than >>> they did in practice. They inevitably interfered with normal browser >>> operation as well as oth

Re: [whatwg] Form submission progress display by UA (incl. file upload)

timeless wrote: > On 1/24/08, Mikko Rantalainen <[EMAIL PROTECTED]> wrote: >> I think that WF2 section 5.6 >> (http://www.whatwg.org/specs/web-forms/current-work/#methodAndEnctypes) >> should be modified to say something along the lines >> >> "User ag

[whatwg] Form submission progress display by UA (incl. file upload)

Consider a form with a file input. User selects a huge file and hits submit. Most UAs do not display nothing but an animated throbber until the full submit is done and the download progress bar only starts to do anything after the full submit part is already done. An another example could be a long

Re: [whatwg]

Brenton Strine wrote: > [IE8] won't render pages with > the new standards-compatibility unless you explicitly > tell it to with this meta tag: > > > My thought is this (and I'm hoping other people will come > up with better ideas). Give HTML the ability to declare > specific technologies that it

Re: [whatwg] Ogg Theora vs H.264

Ian Hickson wrote: > On Wed, 12 Dec 2007, Jeff McAdams wrote: >> Ian Hickson wrote: >>> Ogg isn't a choice, unfortunately. I agree that little choice remains, >>> though. But this is an open issue, and experts in the field are >>> actively trying to resolve it to everyone's satisfaction. >> Yes,

[whatwg] web-apps: API for text field selections is lacking

The section 5.6.2. APIs for the text field selections http://www.whatwg.org/specs/web-apps/current-work/#textFieldSelection defines attributes selectionStart and selectionEnd and method setSelectionRange(). These features are enough to identify the selected data and possibly modify the contents

Re: [whatwg] De-emphasis

David Latapie wrote: On Fri, 09 Feb 2007 12:58:35 +0200, Mikko Rantalainen wrote: ignore and is usually orthogonal to the rest of the content. is something you usually skip but you must be aware of the content (e.g. a copyright or license boilerplate) - the key here is that the content is

Re: [whatwg] De-emphasis

David Latapie wrote: On Thu, 8 Feb 2007 19:09:24 +, Nicholas Shanks wrote: My concern here is whether this is supposed to be an absolute or relative value. Would this result in an emphasis level of 2 (relative) or −1 (absolute). What would level="+3" mean? • I'd say: *default is 0*, so y

Re: [whatwg] The m element

Sarven Capadisli wrote: re: http://www.whatwg.org/specs/web-apps/current-work/#the-m Following is a conversation from #whatwg on freenode. if anyone would like to explain the `m` element further, i'd appreciate it. couldn't get much info out of the whatwg Archives you use it to mark text '

Re: [whatwg] Hyphenation

Øistein E. Andersen wrote: Hyphenation does not seem to have been discussed on this list so far, and I think it should be. General discussion: [1] http://www.w3.org/International/O-HTML-hyphenation.html Old proposal: [2] http://www.nada.kth.se/i18n/html/hyph.html [...] The proposal [2]

Re: [whatwg] finding a number...

Charles McCathieNevile wrote: On Wed, 13 Dec 2006 13:17:14 +0530, Henri Sivonen <[EMAIL PROTECTED]> wrote: On Dec 13, 2006, at 08:32, Charles McCathieNevile wrote: possible *and no simpler* - this is too simple. Maybe assuming you can parse numbers out of text is just a dumb idea as a normativ

Re: [whatwg] Inferring rel="feed" from the media type

Ian Hickson wrote: On Wed, 29 Nov 2006, Mark Baker wrote: And to answer your other question, the proposed new media type for Atom entry documents would only solve the problem for entries. It wouldn't solve them for the MHTML-like Atom document I described, nor any other non-feed use of Atom.

Re: [whatwg] semantics (and dialogue)

Henri Sivonen wrote: HTML+ used for dialog. As far as default presentation goes, is the best fit for marking up dialog. Yet, the semantic markup party line is against it. I think there are two reasons for insisting that shouldn't be used for dialogs, i.e. that really is a definition li

Re: [whatwg] Spellchecking mark III

The more I think about this the more I believe that the correct choise would be to describe the expected content more accurately. The UA may then proceed to accurately turn spellchecking on or off. The problem is that the lang attribute allows only stuff defined in RFC 3066, which seems to supp

Re: [whatwg]

Lachlan Hunt wrote: L. David Baron wrote: We might want to use the accept attribute in the future to indicate what types of content can be sent, and thus what types of input the user agent should allow. Overloading that to get a boolean for whether spellchecking should be enabled seems broken.

Re: [whatwg] The problem of duplicate ID as a security issue

Alexey Feldgendler wrote: The problem of duplicate ID isn't just another issue where it's nice to have some well-defined error recovery just for uniformity. There are cases when duplicate IDs should be viewed as a security concern. [...] For example, imagine a script which finds a button by

Re: [whatwg] Targetting different anchors after submitting the form

Ric Hardacre wrote: Ian Hickson wrote: On Mon, 6 Mar 2006, Mikko Rantalainen wrote: Perhaps something along the lines With WF2 you can just do: indeed: 2.17. Extensions to the submit buttons ... In some cases, authors would like to be able to submit a form to

[whatwg] Targetting different anchors after submitting the form

Currently it's possible to do stuff like this and the UA scrolls down to element with id "anchor" on the page returned by the server. It would be nice to be able to set target anchor on per-submit-button basis. Perhaps something along the lines would result to action urls "url#xfoo

Re: [whatwg] Tag Soup: Blocks-in-inlines

Lachlan Hunt wrote: XYZ Mozilla: BODY + EM + P + SPAN + H1 + EM + #text: X + #text: YZ That look reasonably like what the author would want with that rubbish, except that the Z is within the span, but it's not in the markup. If you swap with ,

Re: [whatwg] [WA1] INS/DEL and omitted tags

Ian Hickson wrote: On Thu, 24 Nov 2005, Simon Pieters wrote: foobar Opera/9.0 (Windows NT 5.1; U; en) foobar Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051120 Firefox/1.6a1 foobar And Safari does what Opera does, which is why it's correct. If either Opera or Safari

Re: [whatwg] [WA1] is semantic

dolphinling wrote: Matthew Thomas wrote: I'd also like to see It is especially semantically important in legal documents (for the same reasons start= is). I agree that making sure the numbering is correct in legal documents (and other documents that have the same type of structure) is seman

Re: [whatwg] [WA1] is semantic

Simon Pieters wrote: Hi, I think that should allow a type attribute as in HTML4[1]. An 1,2,3 list is different from an a,b,c list. If you want to discuss a particular list item in the text then it doesn't make sense to say "f" when the list says "6", for instance. Consider the following real