On Tue, 10 Feb 2009 11:52:32 +0100, Ian Hickson i...@hixie.ch wrote:
Speaking of hr, having a default style for it would increase
interoperability (if only in the presentation layer) a great deal.
Done.
Excellent!
--
Asbjørn Ulsberg -=|=- asbj...@ulsberg.no
«He's a
On Fri, 06 Apr 2007 02:22:52 +0200, Sander Tekelenburg [EMAIL PROTECTED]
wrote:
Surely we're not trying to ensure that a Web page
is presented the same in every browsing environment? What would be the
use of that?
That's what people expect from us (browser vendors).
Which people?
Our
At 09:54 +0200 UTC, on 2007-04-02, Anne van Kesteren wrote:
On Mon, 02 Apr 2007 09:59:50 +0200, Sander Tekelenburg [EMAIL PROTECTED]
wrote:
[...]
Surely we're not trying to ensure that a Web page
is presented the same in every browsing environment? What would be the
use of that?
That's
At 16:20 +0200 UTC, on 2007-04-02, Thomas Broyer wrote:
2007/4/2, Asbjørn Ulsberg:
[...]
Should the HTML or CSS specification then encourage HTML and CSS authors
to use such a zapper to get expected visual results across browsers?
Why not, but such a zapper should then be given in the
At 12:52 +0200 UTC, on 2007-04-02, Asbjørn Ulsberg wrote:
On Mon, 02 Apr 2007 09:59:50 +0200, Sander Tekelenburg [EMAIL PROTECTED]
wrote:
[display: block and inline]
Defining preseantation up to *that* level is no problem IMO.
Great! Then let's.
The current (HTML 4) spec already does
At 03:18 -0400 UTC, on 2007-04-02, Mike Schinkel wrote:
Sander Tekelenburg wrote:
[...]
What exactly, in the context of presentation, would be good about
consistency
*across* UAs?
See Jakob's Law of Internet User Experience
http://www.useit.com/alertbox/2723.html
I fail to see the
[Mike, you are making the communication more difficult by changing the
Subject header without a good reason. Doing so fragments the discussion,
makes it harder for people to keep track of what is said in relation to what.
I'm changing the Subject back to what it was.]
At 00:13 -0400 UTC, on
At 19:30 +0200 UTC, on 2007-04-01, Anne van Kesteren wrote:
On Sun, 01 Apr 2007 20:16:12 +0200, Sander Tekelenburg [EMAIL PROTECTED]
wrote:
Who are we (as spec definers) to decide that x is the only correct
behaviour or presentation? And why should we want to stifle innovation
by requiring
On Sun, 01 Apr 2007 12:35:02 +0200, Kempen, E.J.F. van
[EMAIL PROTECTED] wrote:
What exactly are you looking for? Defining that 'normal' text is black
by default and links are blue-ish? Because that's done already, most
default styles are uniformly, but maybe informally, defined.
Where?
On Mon, 02 Apr 2007 09:54:04 +0200, Anne van Kesteren [EMAIL PROTECTED]
wrote:
The default style of hr, p, table, et cetera.
Speaking of hr, having a default style for it would increase
interoperability (if only in the presentation layer) a great deal.
Defining what a hr *is* in terms
2007/4/2, Asbjørn Ulsberg:
That translation already leads to a plethora of different results,
CSS-wise. Is the whitespace around a p margin or padding?
According to http://www.w3.org/TR/CSS2/sample.html this is margin.
What is the default style of li elements? Do they have outside or inside
On Mon, 02 Apr 2007 16:05:19 +0200, Nicholas Shanks
[EMAIL PROTECTED] wrote:
With CSS2.1, how would you style the button you get from an input
type=file for instance?
I don't know about other UAs, but in Safari one would use the selector:
input[type=file]::-webkit-file-upload-button
My
[mailto:[EMAIL PROTECTED] On Behalf Of Asbjørn Ulsberg
While HTML is a semantic markup language, it's not something
to ignore that it's mostly used for visual rendering of
content, often accompanied by a CSS document. While I'm a
strong believer of separation between structure (HTML),
On Sun, 01 Apr 2007 04:28:54 +0200, Lachlan Hunt
[EMAIL PROTECTED] wrote:
I think there might be room to discuss the inclusion of default CSS
(perhaps even Aural CSS) fragments in the specification as well.
Yes, that will be defined in due course.
Excellent!
P.S. There was no need to
Kempen, E.J.F. van wrote:
What exactly are you looking for? Defining that 'normal' text is black by
default and links are blue-ish? Because that's done already, most default
styles are uniformly, but maybe informally, defined.
One example that springs to mind is that the default CSS rules
At 03:38 +0200 UTC, on 2007-04-01, Asbjørn Ulsberg wrote:
[...]
While I'm a strong believer of separation between
structure (HTML), presentation (CSS) and functionality (JavaScript), I
think it could be useful for the HTML specification to -- within limits --
define how each and every
On Sun, 01 Apr 2007 20:16:12 +0200, Sander Tekelenburg [EMAIL PROTECTED]
wrote:
Who are we (as spec definers) to decide that x is the only correct
behaviour or presentation? And why should we want to stifle innovation
by requiring
some specific presentation?
Defining default rendering for
Since having informal Relax-NG schema fragments in the HTML specification
has been discussed, I think there might be room to discuss the inclusion
of default CSS (perhaps even Aural CSS) fragments in the specification as
well.
While HTML is a semantic markup language, it's not something to
Asbjørn Ulsberg wrote:
I think there might be room to discuss the inclusion of default CSS
(perhaps even Aural CSS) fragments in the specification as well.
Yes, that will be defined in due course.
http://www.whatwg.org/specs/web-apps/current-work/#rendering
P.S. There was no need to cross
19 matches
Mail list logo
