Re: [whatwg] Where did the rev attribute go?
On 7/5/06, Ian Hickson [EMAIL PROTECTED] wrote: (This data is based on a crawl of approximately one billion documents.) Could you give us some pointers to this software? Could you give us pointers to that data? -- Hugh Winkler Wellstorm Development http://www.wellstorm.com/ +1 512 694 4795 mobile (preferred) +1 512 264 3998 office
Re: [whatwg] Where did the rev attribute go?
On Thu, 6 Jul 2006, Hugh Winkler wrote: On 7/5/06, Ian Hickson [EMAIL PROTECTED] wrote: (This data is based on a crawl of approximately one billion documents.) Could you give us some pointers to this software? Could you give us pointers to that data? http://code.google.com/webstats/index.html -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] Spellchecking mark III
Ian Hickson wrote: 3. Otherwise, if the user has disabled the checking for this text, then the checking is disabled. 4. Otherwise, if the user has forced the checking for this text to always be enabled, then the checking is enabled. 5. Otherwise, if the element with which the text is associated has a spellcheck content attribute, then: if that attribute has the literal value on, then checking is enabled; otherwise, if that attribute has the literal value off, then checking is disabled; otherwise, move on to the next step. How does this get away from the Check Spelling: ( ) No ( ) Yes(i.e. when the page says) ( ) Really, really, yes(i.e. always, whatever the page says) preference problem? Gerv
Re: [whatwg] form validation of values that aren't entered by the user
On 01/02/06, Hallvord Reiar Michaelsen Steen [EMAIL PROTECTED] wrote: I've already brought up this issue because of the kayak.com search fields with a maxlength smaller than the length of the strings scripts would insert into the input elements. This problem is more serious than we thought at first. Many ASP.NET sites wrap the entire page in a FORM that is submitted from JavaScript as part of site navigation. The spec as it stands will prevent navigation on any ASP.NET site combining maxlength and a hint text longer than it. For example input maxlength=5 name=zip value=Zip code prevents navigating costco.com . Know you're working on web apps mostly these days, Ian, but I hope you get a chance to rework this before more UAs implement it. Proposed changes to the spec: under tooLong I suggest this: and the control has more than the specified number of code points changed to the control's value is not its defaultValue and the control has more than the specified number of code points -- Hallvord R. M. Steen
[whatwg] [WF2] validating things the user can't change..
Another couple of comments regarding validation: * willValidate IMO should not be true for readonly elements. The user can't change them anyway, so what's the point of reporting validation errors to the user? * same with INPUT type=hidden (is it excluded already?) Suggestion: after the line liThe control is not spana href=#disableddisabled/a/span. add the following: liThe control is not spana href=#readonlyreadonly/a/span. liThe control's type attribute is not hidden. -- Hallvord R. M. Steen
Re: [whatwg] Canvas 2d methods
Vladimir Vukicevic wrote: Even without using |with|, why not just create a simple JS wrapper for the context object that can have return-this or any other desired semantics? This is possible, but I consider the canvas implementation as too performance critical to slow it down by such a wrapper. I could live with it, if it were to use only for some upgrading time. This would avoid a change that would have some apps require canvas 2D 2.0 or some such, and require authors to do version checks to see which version of canvas is supported -- and still write old code for quite some time. You are arguing here generally against any possible extension of the API in the future. Please note, that this minor change of the API does not affect existing code. Adding a different way to do the same things that can be done now without much benefit in simplicity or efficiency doesn't seem useful. Some users on this list -- me included -- and a certain part of the future user base of the canvas element may see a benefit in familiar coding style which they might call simplicity. The benefit in efficiency might be significant due to optimizing interpreters, but is measurable only with at least one implementation. Canvas supports multiple contexts for a reason; if there are compelling arguments for a complete rev of the 2D API, then a new context can be introduced to support that. Great feature of Canvas to support multiple contexts. I would welcome the introduction of such a new context. -- Stefan Gössner http://goessner.net
