![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||||
| |||||
|
|
In article <user-461ADB.09280129122004 (AT) news (DOT) euro.net>, Sander Tekelenburg <user (AT) domain (DOT) invalid> wrote: |
|
I was wondering whether an empty SPAN with a background image and explicit width is a valid construction. It the syntactic sense it is valid. I use that construction at <http://www.lotzofmusic.com/>. Mozilla 1.7.5, Opera 7.5.4 and iCab 3.0 happily deal with this the way I hoped Only because the display property computes to block, because you have set float: left;. |
|
http://www.w3.org/TR/CSS21/visuren.html#dis-pos-flo |
|
But then why does the W3C validator not complain? Declaring properties that do not apply in some situations is not a syntax error. |
Thanks.|
[The reason I posted this to ciwah, in spite of all the CSS involved, was that it seemd to be about elements and thus about HTML.] This is all CSS stuff. |
#2
| |||
| |||
|
|
Only because the display property computes to block, because you have set float: left;. Yes, that would make sense. However, I don't see that confirmed by http://www.w3.org/TR/CSS21/visuren.html#dis-pos-flo which says "[...] if 'float' has a value other than 'none', the box is floated and 'display' is set according to the table below [...]". Then in 'the table below' it seems to say that in this case display is set to "same as specified". Eh? |
#3
| |||
| |||
|
|
In article <user-D52580.07201730122004 (AT) news (DOT) euro.net>, Sander Tekelenburg <user (AT) domain (DOT) invalid> wrote: |
|
Eh? The table says that when the specified value is 'inline', the computed value is 'block'. |
#4
| |||
| |||
|
|
Ah. I think I understand. I got thrown off by the *specified* in "specified value" - I haven't specified an inline value for the SPANs. But of course a SPAN's default value _is_ inline. So the 'specified' value is inline. I guess that's the 'logic' of the phrasing there, right? |
#5
| |||
| |||
|
|
In article <user-7DBA25.13062130122004 (AT) news (DOT) euro.net>, Sander Tekelenburg <user (AT) domain (DOT) invalid> wrote: Ah. I think I understand. I got thrown off by the *specified* in "specified value" [...] "Specified value" is a defined term in CSS 2.1: http://www.w3.org/TR/CSS21/cascade.html#specified-value |

#6
| |||
| |||
|
|
In article <hsivonen-8BC878.15523930122004 (AT) news (DOT) dnainternet.net>, Henri Sivonen <hsivonen (AT) iki (DOT) fi> wrote: In article <user-7DBA25.13062130122004 (AT) news (DOT) euro.net>, Sander Tekelenburg <user (AT) domain (DOT) invalid> wrote: Ah. I think I understand. I got thrown off by the *specified* in "specified value" [...] "Specified value" is a defined term in CSS 2.1: http://www.w3.org/TR/CSS21/cascade.html#specified-value Well I'll be damned... Thanks! ![]() Was there any way I should have been able to realise to even look for and then find that? |
|
(To be honest, in a specification I would expect something like this[*] to be marked up and presented in a useful manner. Preferably with a hyperlink pointing to the definition.) |
![]() |
| Thread Tools | |
| Display Modes | |
| |