Re: [whatwg] [html5] Rendering of interactive content

2009-04-26 Thread Ian Hickson
On Thu, 12 Feb 2009, Giovanni Campagna wrote: 2009/2/11 Ian Hickson i...@hixie.ch 2) you depend on css3-ui, in CR stage, instead of becss, a very early WD BECSS is actually probably more stable than CSS3 UI at this point. Why do you say so? Will CSS3 UI go back to

Re: [whatwg] [html5] Rendering of interactive content

2009-02-12 Thread Giovanni Campagna
2009/2/11 Ian Hickson i...@hixie.ch [...] 2) you depend on css3-ui, in CR stage, instead of becss, a very early WD BECSS is actually probably more stable than CSS3 UI at this point. Why do you say so? Will CSS3 UI go back to Last Call or BECSS process to Last Call in the

Re: [whatwg] [html5] Rendering of interactive content

2009-02-11 Thread Aryeh Gregor
On Tue, Feb 10, 2009 at 10:30 PM, Ian Hickson i...@hixie.ch wrote: If the UA suddenly displays hyperlinks in green and I decided that my background is green, the user will complain with me, not with the UA (and will probably switch to a different website) Authors should never the background

Re: [whatwg] [html5] Rendering of interactive content

2009-02-11 Thread Smylers
Aryeh Gregor writes: On Tue, Feb 10, 2009 at 10:30 PM, Ian Hickson i...@hixie.ch wrote: If the UA suddenly displays hyperlinks in green and I decided that my background is green, the user will complain with me, not with the UA (and will probably switch to a different website)

Re: [whatwg] [html5] Rendering of interactive content

2009-02-11 Thread Aryeh Gregor
On Wed, Feb 11, 2009 at 8:36 AM, Smylers smyl...@stripey.com wrote: That is precisely an instance of an author setting a background colour without a foreground colour -- specifically the author set the background colour used on links without setting the foreground colour for links. . . .

Re: [whatwg] [html5] Rendering of interactive content

2009-02-11 Thread Boris Zbarsky
Smylers wrote: That is precisely an instance of an author setting a background colour without a foreground colour -- specifically the author set the background colour used on links without setting the foreground colour for links. If an author sets a background colour then she needs to set the

Re: [whatwg] [html5] Rendering of interactive content

2009-02-11 Thread Smylers
Aryeh Gregor writes: On Wed, Feb 11, 2009 at 8:36 AM, Smylers smyl...@stripey.com wrote: That is precisely an instance of an author setting a background colour without a foreground colour -- specifically the author set the background colour used on links without setting the foreground

Re: [whatwg] [html5] Rendering of interactive content

2009-02-11 Thread Aryeh Gregor
On Wed, Feb 11, 2009 at 10:13 AM, Smylers smyl...@stripey.com wrote: Ah, I see. Thanks for explaining that. I'm interpreting it as for each bit of text that you cause the background colour to be set for, also specify its foreground colour (and _vice versa_). But that's not *possible* in CSS.

Re: [whatwg] [html5] Rendering of interactive content

2009-02-11 Thread Smylers
Aryeh Gregor writes: On Wed, Feb 11, 2009 at 10:13 AM, Smylers smyl...@stripey.com wrote: Ah, I see. Thanks for explaining that. I'm interpreting it as for each bit of text that you cause the background colour to be set for, also specify its foreground colour (and _vice versa_). But

Re: [whatwg] [html5] Rendering of interactive content

2009-02-10 Thread Ian Hickson
On Sat, 7 Feb 2009, Giovanni Campagna wrote: 2009/2/6 Ian Hickson i...@hixie.ch On Fri, 6 Feb 2009, Giovanni Campagna wrote: I'm proposing to replace the current rendering mechanism, based on Behavioural Extension to CSS, that in turn is based on XBL2, with something based on the

Re: [whatwg] [html5] Rendering of interactive content

2009-02-09 Thread Giovanni Campagna
@Smylers: So the whole rendering section is just for implementors and authors should act if no default style sheet is present or worse, if it could be everything, like a inline-block div or blue table, so that the author should set all supported properties to initial or the HTML5 expected value?

Re: [whatwg] [html5] Rendering of interactive content

2009-02-09 Thread Smylers
Giovanni Campagna writes: So the whole rendering section is just for implementors and authors should act if no default style sheet is present No; the section is also for authors, in that it advises them of how content is expected to be rendered in mainstream graphical browsers. or worse, if

Re: [whatwg] [html5] Rendering of interactive content

2009-02-09 Thread Giovanni Campagna
2009/2/9 Smylers smyl...@stripey.com Giovanni Campagna writes: So the whole rendering section is just for implementors and authors should act if no default style sheet is present No; the section is also for authors, in that it advises them of how content is expected to be rendered in

Re: [whatwg] [html5] Rendering of interactive content

2009-02-08 Thread Giovanni Campagna
2009/2/8 Benjamin Hawkes-Lewis bhawkesle...@googlemail.com On 7/2/09 20:07, Giovanni Campagna wrote: Yes, but what properties should I query for? In order to find out what, precisely? What to reset, for example (see the first Ian email on this topic) Binding, behaviour, appearance,

Re: [whatwg] [html5] Rendering of interactive content

2009-02-08 Thread Boris Zbarsky
Giovanni Campagna wrote: Could you propose an example of this UA, that still preserves the semantics of the elements, as required by HTML5? A UA that differentiates, in its default styling, between same-site links and links to a different site. -Boris

Re: [whatwg] [html5] Rendering of interactive content

2009-02-08 Thread Smylers
Giovanni Campagna writes: If input type=submit in some UA is rendered with all properties set to initial, not only it does not express the semantic of a button, but it may be difficult for a user to actually recognize it as a button and eventually click it. In that case I, as the author, may

Re: [whatwg] [html5] Rendering of interactive content

2009-02-08 Thread Giovanni Campagna
2009/2/8 Smylers smyl...@stripey.com Giovanni Campagna writes: If input type=submit in some UA is rendered with all properties set to initial, not only it does not express the semantic of a button, but it may be difficult for a user to actually recognize it as a button and eventually

Re: [whatwg] [html5] Rendering of interactive content

2009-02-08 Thread Smylers
Giovanni Campagna writes: 2009/2/8 Smylers smyl...@stripey.com Giovanni Campagna writes: data:text/html,stylelabel { position:fixed; top:-1em; border:1px solid black; } label input { -moz-appearance:none; -webkit-appearance:none; border:none; width:auto; } input[type=submit] {

Re: [whatwg] [html5] Rendering of interactive content

2009-02-08 Thread Benjamin Hawkes-Lewis
On 8/2/09 13:18, Giovanni Campagna wrote: 2009/2/8 Benjamin Hawkes-Lewis bhawkesle...@googlemail.com mailto:bhawkesle...@googlemail.com On 7/2/09 20:07, Giovanni Campagna wrote: Yes, but what properties should I query for? In order to find out what, precisely? What to reset,

Re: [whatwg] [html5] Rendering of interactive content

2009-02-08 Thread Benjamin Hawkes-Lewis
On 8/2/09 14:38, Giovanni Campagna wrote: Having somewhere written that hyperlinks should be blue, allows you to style the background-color to anything but blue. If the UA suddenly displays hyperlinks in green and I decided that my background is green, the user will complain with me, not with

Re: [whatwg] [html5] Rendering of interactive content

2009-02-07 Thread Giovanni Campagna
2009/2/6 Ian Hickson i...@hixie.ch On Fri, 6 Feb 2009, Giovanni Campagna wrote: I'm proposing to replace the current rendering mechanism, based on Behavioural Extension to CSS, that in turn is based on XBL2, with something based on the CSS3 Basic User Interface (css3-ui), ie replacing

Re: [whatwg] [html5] Rendering of interactive content

2009-02-07 Thread Benjamin Hawkes-Lewis
On 7/2/09 14:22, Giovanni Campagna wrote: 5) becss requires one or more binding languages: it is not necessarily XBL2, but currently XBL2 is the only one available: are you constraining the implementation of HTML5 on that of XBL2? The rendering section has no

Re: [whatwg] [html5] Rendering of interactive content

2009-02-07 Thread Giovanni Campagna
2009/2/7 Benjamin Hawkes-Lewis bhawkesle...@googlemail.com On 7/2/09 14:22, Giovanni Campagna wrote: 5) becss requires one or more binding languages: it is not necessarily XBL2, but currently XBL2 is the only one available: are you constraining the implementation of

Re: [whatwg] [html5] Rendering of interactive content

2009-02-07 Thread Benjamin Hawkes-Lewis
On 7/2/09 18:51, Giovanni Campagna wrote: So the rendering section imposes *no* requirements on HTML5 conforming user agents, therefore the spec is not constraining the implementation of HTML5 on that of XBL2. Yes, but UA that don't follow that set of CSS rules are not

Re: [whatwg] [html5] Rendering of interactive content

2009-02-07 Thread Giovanni Campagna
2009/2/7 Benjamin Hawkes-Lewis bhawkesle...@googlemail.com On 7/2/09 18:51, Giovanni Campagna wrote: So the rendering section imposes *no* requirements on HTML5 conforming user agents, therefore the spec is not constraining the implementation of HTML5 on that of XBL2. Yes, but UA

Re: [whatwg] [html5] Rendering of interactive content

2009-02-07 Thread Benjamin Hawkes-Lewis
On 7/2/09 20:07, Giovanni Campagna wrote: Yes, but what properties should I query for? In order to find out what, precisely? Binding, behaviour, appearance, border, color, font, all in once? And what should their values be? Their values depend on user agent defaults (which may be

[whatwg] [html5] Rendering of interactive content

2009-02-06 Thread Giovanni Campagna
I'm proposing to replace the current rendering mechanism, based on Behavioural Extension to CSS, that in turn is based on XBL2, with something based on the CSS3 Basic User Interface (css3-ui), ie replacing the binding: property with appropriate appearance: property directly on the element, instead

Re: [whatwg] [html5] Rendering of interactive content

2009-02-06 Thread Ian Hickson
On Fri, 6 Feb 2009, Giovanni Campagna wrote: I'm proposing to replace the current rendering mechanism, based on Behavioural Extension to CSS, that in turn is based on XBL2, with something based on the CSS3 Basic User Interface (css3-ui), ie replacing the binding: property with appropriate