Re: [whatwg] whatwg Digest, Vol 33, Issue 90

2006-12-28 Thread FROIDURE Nicolas 

 Hi,

  I don't know if you ever talk about that, but some things seems 
important to me for the next HTML version :

Web forms :
   - 2 attributes for  : max (like other fields) and type (to 
specify a text mime type for the content edition bbcode, html, xhtml, 
xbbcode etc...). It will be a good way to improve the quality of the web 
by *improving the quality of user interventions*.
   - 1 attribute for  : autocomplete (it exists in XUL, a value 
could be an URL to load when some contain is typed).

Semantic :
   - 1 attribute for code : type.
   - maybe an attribute for em and strong. Something like "degree" and 
a numeric value to notice the emphase degree of the sentences.


Regards, Nicolas FROIDURE.
http://bbcomposer.eliwork.com

[whatwg] scrolling

2006-12-28 Thread Neil Deakin 
Right now there isn't any specification for retrieving or modifying the 
scroll position of a scrollable area. There's a brief mention of the 
scroll* properties as part of the CSS object model draft [1] but I'm not 
sure if the css wg is the right place for that work, or whether this 
would better be part of the Web Applications spec either current or 
future. Regardless, I've written a proposal at [2] for how the scroll* 
properties could work as well as notes about how existing browsers 
handle them. Thoughts?


[1] http://dev.w3.org/cvsweb/~checkout~/csswg/cssom/Overview.src.html
[2] http://xulplanet.com/ndeakin/xul/specs/scrollspec.html

Neil

Re: [whatwg] [WebApps] canvas transform()/setTransform()

2006-12-28 Thread Charles McCathieNevile 
On Thu, 28 Dec 2006 03:02:05 +0100, 黒澤剛志(KUROSAWA, Takeshi)  
<[EMAIL PROTECTED]>

wrote:


Dear WHATWG,

Web Application 1.0 adds the transform() and the setTransform() to the
canvas 2d context.
The conversion of the arguments of these methods to the matrices is
described in the section 3.14.6.1.2.

The transform(m11, m12, m21, m22, dx, dy) method must multiply the 
current transformation matrix with the matrix described by:

m11 m12 dx
m21 m22 dy
0 0 1

The setTransform(m11, m12, m21, m22, dx, dy) method...

- http://www.whatwg.org/specs/web-apps/current-work/#transform

...the matrix should be

m11 m21 dx
m12 m22 dy ... (b)
0 0 1


In particular, this would make for easy compatibility with SVG  
transformations,

helping authors to copy them from one to hte other format and back.

cheers

Chaals

--
Charles McCathieNevile, Opera Software: Standards Group
hablo español - je parle français - jeg lærer norsk
[EMAIL PROTECTED] Try Opera 9 now! http://opera.com

Re: [whatwg] Dual mode for client?

2006-12-28 Thread Anne van Kesteren 
On Thu, 28 Dec 2006 10:17:33 +0100, Alexey Feldgendler  
<[EMAIL PROTECTED]> wrote:
The spec defines exactly under what circumstances are parse errors  
generated. I think it's out of scope to define how/whether these parse  
errors are reported.


Agreed. Also, as discussed on this list it doesn't make sense for all user  
agents to report these results.



--
Anne van Kesteren

Re: [whatwg] Dual mode for client?

2006-12-28 Thread Alexey Feldgendler 
On Wed, 27 Dec 2006 01:28:59 +0600, Mike Schinkel <[EMAIL PROTECTED]>  
wrote:


I'm wondering if you collectively would consider adding the following to  
the spec; a recommendation that clients offer two "modes"; one mode  
being for
users where the spec works as currently envisioned. The second mode  
would be for web developers and would generate errors for invalid markup  
as opposed to generating no errors (Ian had said it was preferred to not  
generate
errors for invalid markup to ensure users were willing to use browsers  
based on the newer spec; a dual mode would give the best of both worlds.)


The spec defines exactly under what circumstances are parse errors  
generated. I think it's out of scope to define how/whether these parse  
errors are reported.



--
Alexey Feldgendler <[EMAIL PROTECTED]>
[ICQ: 115226275] http://feldgendler.livejournal.com