Re: [css-d] understading ul li as menus - A 5 question quest.
Thank you all for your replies, again.:) I needed some time to test and
think a little...
1)
If we apply overflow property here, will this property
be inherited to descendants even without being declared
on them as inherit ?
see
http://www.w3.org/TR/CSS21/visufx.html#propdef-overflowhttp://www.w3.org/TR/CSS21/visufx.html#propdef-overflow
see
Inherited: no
Clear. :)
2)
How do we call the properties that have this inheritance
capacities?
Having inheritance is something that some properties may
have by default, or the user agents are the responsible
for giving that to some properties?
2.
http://www.w3.org/TR/CSS21/cascade.html#inheritancehttp://www.w3.org/TR/CSS21/cascade.html#inheritance
Each property defines whether it is inherited or not.
see the Inherited? column here
http://www.w3.org/TR/CSS21/propidx.htmlhttp://www.w3.org/TR/CSS21/propidx.html
No doubts here as well, btw, this last link is a very useful table.
3.1)
I see that, to solve it, we can use the float property to
eliminate that extra space between inline elements.
Why is that? Is it because the float property tell us
by definition, that if we have, for example, 3 floated
elements they will/should place themselves on the outer
edge of the previous floated element or container?
Ingo already gave you an explanation for what that space is
(white-space nodes in the html mark-up)
When you float the element or otherwise set to to display block,
html parsing rules kicks in, and basically those nodes are
suppressed for display purposes.
A lot to discover here. What are those white-space nodes on html ? What
other white-space nodes can we find? Why inline accepts those white spaces
and block elements don't ? Is this something to do with box-model ? Does the
box model apply to inline elements? Why has a markup language white spaces?
I realize this is to many questions with two many uncovered holes. I will
try to clarify them with the list help, with time, if you all allow.
David Laakso and others, I was clearly unable to represent the intended
result, this works, either in navegacao class or on the ul related :
.navegacao
{
padding: 20px 0.5em; background: #eee;
float:right;
margin-top:2.5em;
margin-right:0.5em;
overflow:hidden;
}
But the intended result was something more like this:
http://www.nuvemk.com/formacao_lx/outros/ul_li_tests_v2.html
to accomplish this, I have add padding to the a element.
4)
On the - .navegacao ul li a - declaration block,
we can't add padding-top and bottom, they will not be
rendered on the viewport. Why? Because we are treat them
as inline elements and not, block box elements.
Is this precise?
Why line-height doesn't work either?
the parent UL DIV are set to 'overflow:hidden', the a elements are
set to display: inline. The padding (top and or bottom) is applied to the
elements, but because it is an inline element, the
excess padding will be clipped by the overflow:hidden.
Ok. But if I remove the display:inline; should the padding-top and bottom of
those elements (that are no longer inline), be rendered on the viewport,
despite the overflow:hidden; declaration ?
If I remove only the display:inline; and I keep the overflow:hidden; I still
can't see the padding effects:
http://www.nuvemk.com/formacao_lx/outros/ul_li_tests_v3.html
Line-height should affect the layout though.
and if I remove the padding declarations and try to do it with line-height
property, I still can't see any effects on the vertical space augmentation:
http://www.nuvemk.com/formacao_lx/outros/ul_li_tests_v4.html
So, I still have doubts here:
but because it is an inline element, the
excess padding will be clipped by the overflow:hidden.
because it seems that, even if we remove the display:inline; property, the
padding is still clipped,if we keep that overflow:hidden; declaration.
Since to accomplish this,
http://www.nuvemk.com/formacao_lx/outros/ul_li_tests_v2.html
we need to remove the overflow:hidden; declarations, may I presume that, on
this case, this is not the proper hasLayout trigger to sue?
In your opinion, what effective hasLayout trigger can be used here?
Thanks you all,
Márcio
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] IE8 bidi and hasLayout
Hello all, It appears that MS has hacked in bidirection (somewhat improved over IE7) by the use of *hasLayout*. http://css-class.com/test/bugs/ie/ie8-haslayout-bidi.htm Will they ever cease to make us wonder. -- Alan http://css-class.com/ Armies Cannot Stop An Idea Whose Time Has Come. - Victor Hugo __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] IE8 bidi and hasLayout
It appears that MS has hacked in bidirection (somewhat improved over IE7) by the use of *hasLayout*. http://css-class.com/test/bugs/ie/ie8-haslayout-bidi.htm Hi Alan, In what build? The first examples look good to me in IE8 (8.0.7600.16385), but using IE8 via IE tester I do see the issues you describe. -- Regards, Thierry www.tjkdesign.com | articles and tutorials www.ez-css.org | ultra light CSS framework __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] understading ul li as menus - A 5 question quest.
2010/3/7 Benoit Favreault b...@provokat.ca we need to remove the overflow:hidden; declarations, may I presume that, on this case, this is not the proper hasLayout trigger to sue? In your opinion, what effective hasLayout trigger can be used here? On floats, display : inline is a good hasLayout trigger. It won't be effectively applied because floats are always in block display mode (but the declaration triggers hasLayout anyway), so you can keep using your floats as blocks. Hope this help Benoit Favreault Provokat.ca __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] IE8 bidi and hasLayout
It appears that MS has hacked in bidirection (somewhat improved over IE7) by the use of *hasLayout*. http://css-class.com/test/bugs/ie/ie8-haslayout-bidi.htm Hi Alan, In what build? The first examples look good to me in IE8 (8.0.7600.16385), but using IE8 via IE tester I do see the issues you describe. Thanks to Theophan who sent me a screenshot off-list I found out that your page was rendered in IE7 compatibility mode. So IE Tester was right. -- Regards, Thierry www.tjkdesign.com | articles and tutorials www.ez-css.org | ultra light CSS framework __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] understading ul li as menus - A 5 question quest.
2010/3/7 Benoit Favreault b...@provokat.ca we need to remove the overflow:hidden; declarations, may I presume that, on this case, this is not the proper hasLayout trigger to sue? In your opinion, what effective hasLayout trigger can be used here? On floats, display : inline is a good hasLayout trigger. It won't be effectively applied because floats are always in block display mode (but the declaration triggers hasLayout anyway), so you can keep using your floats as blocks. I didn't follow this thread, but the above is incorrect. floats always *have* a layout. afaik, display:inline is not used to trigger hasLayout, but to prevent the double margin bug. -- Regards, Thierry www.tjkdesign.com | articles and tutorials www.ez-css.org | ultra light CSS framework __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] FW: bemstrongi tags
Michael Stevens said: My point was that, stricly semantically speaking (real semantics not web semantics), most tags are used to change the way a browser presents text to the reader. That is PRESENTATTIONAL by definition. By you and in your head, yes, that's possible. But the joke is on you. Because many developers don't work like that. Your definition is incomplete and quite useless I think. In the end they almost always change the way the text is presented. So what? Personally, I markup my content semantically in the *structural* fashion that works for me and use CSS to present this content in the fashion I choose. For me HTML is primarily structure and meaning intermingled. Let me say that again: Structure. If browsers choose to present my HTML- structure in a certain way, by CSS defaults when my CSS instructions fail, then that's fine by me. I feel my markup work WITH the browsers way of conveying this structure, not against it. I don't think HTML is perfect in any way, but separating presentation and structure/meaning is way better than the old alternative IMHO. /MB __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] FW: bemstrongi tags
Alan Gresley blurted out: The built-in defaults ARE CSS. It's the CSS the browsermakers decided to have builtin. Technically, this is the case with Firefox anyway. No, you are both wrong in opposite ways. The user agent defaults are just style sheets and an important part in the cascade. That's just another way of saying what I said. What the difference in meaning between The 'built-in defaults' are CSS. and defaults are just style sheets. __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] css-sound joomla templates?
na...@thesmudge.com said: I'm currently using one based on a template from http://www.joomlart.com called ja_rochea. I moved around, eliminated, and added divs, and redid most of the css, so it's not much like the original. But at least it wasn't based on tables, if that's what you mean. Well, I prefer to not use tables for layout nor Divitis-suffering layouts. I'd like templates with lists, when the content is likely to be lists, like for instance lists of articles, navigation and similar, and tables only when the content is likely to be tabular. And so on. HTML may be incomplete, but so be it. On the other hand, a well made DIV-markup based layout may be very easy to change yourself to your type of markup, if it's not a tag soup. It turns out, however, I'm going to write my own publishing engine instead for this assignment, so no Joomla this time. Thanks for your response. /MB __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] IE7 bug with inheritance
Gabriele Romanato wrote: Please read the latest two posts on IE7 on my blog and tell me if I stumbled on something that's well-documented or not. Can you please provide a URL that demonstrates the issue in the simplest possible context? Can you make up a static test? It depends on what the problem is. Can't you make up a static test of the problem you have in your mind? I used JavaScript to create spans in the following structure: ul id=navigation lia href=spanLink/span/a/li /ul Try to apply some styles to :hover: nothing happens to links, but they maintain the same styles specified before. thanks in advance. What happens if you test with the markup above on a static HTML page? If the problem occurs only with JavaScript-generated elements, maybe the problem is in JavaScript code (which might even fail to generate the structure you expect it to generate). The issue might be something else on your page, like any CSS rule setting properties for the span element. If you set color for it, it won't inherit color from its parent, of course. -- Yucca, http://www.cs.tut.fi/~jkorpela/ __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] css-sound joomla templates?
Thanks everyone for your suggestions. It turns out I'm going to write my own publishing engine instead for this assignment, so no Joomla this time. /MB __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] css-sound joomla templates?
At 9:56 PM +0100 3/7/10, MB wrote: Thanks everyone for your suggestions. It turns out I'm going to write my own publishing engine instead for this assignment, so no Joomla this time. /MB That's what I do. Cheers, tedd -- --- http://sperling.com http://ancientstones.com http://earthstones.com __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] Transcendant web design and CSS3
I recently acquired a copy of /Transcending CSS: The Fine Art of Web Design/ by Andy Clarke (New Riders, 2007: ISBN 0-321-41097-1). Mr Clarke is pushing CSS3 in this book, though he notes that (at the time the book was written) support for CSS3 was spotty at best even for the Mac (his preferred platform). He also advocates NOT trying to make the presentation of a website look the same in all browsers, but to write to the limit of the CSS capabilities of each individual browser, and use things like conditional includes, media rules, and @import to control what CSS gets seen/used by which browser(s). Question the first: Is this a widely-accepted philosophy in the web-design community, and is it being widely adopted - and should it be? Question the second: What is the current level of support for CSS3? There are some interesting ideas in CSS3, which I would like to be able to use - but I'd like to know that the support is there and relatively stable before attempting to use it. __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Transcendant web design and CSS3
I recently acquired a copy of /Transcending CSS: The Fine Art of Web
Design/ by Andy Clarke (New Riders, 2007: ISBN 0-321-41097-1).
Mr Clarke is pushing CSS3 in this book, though he notes that (at the
time the book was written) support for CSS3 was spotty at best even for
the Mac (his preferred platform). He also advocates NOT trying to make
the presentation of a website look the same in all browsers, but to
write to the limit of the CSS capabilities of each individual browser,
and use things like conditional includes, media rules, and @import to
control what CSS gets seen/used by which browser(s).
Question the first: Is this a widely-accepted philosophy in the
web-design community, and is it being widely adopted - and should it
be?
I think this is the right approach, but note that most of the time there is
no need to control what is sent to a particular browser as a property which
is not supported is simply ignored.
For example consider this:
.myBox {
border:1px solid #333;
-moz-border-radius:3px;
-webkit-border-radius: 3px;
border-radius: 3px;
}
Question the second: What is the current level of support for CSS3?
There are some interesting ideas in CSS3, which I would like to be able
to use - but I'd like to know that the support is there and relatively
stable before attempting to use it.
This is a great resource:
http://a.deveria.com/caniuse/
--
Regards,
Thierry
www.tjkdesign.com | articles and tutorials
www.ez-css.org | ultra light CSS framework
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Transcendant web design and CSS3
On Mar 8, 2010, at 8:21 AM, Jeff Zeitlin wrote: Mr Clarke is pushing CSS3 in this book, though he notes that (at the time the book was written) support for CSS3 was spotty at best even for the Mac (his preferred platform). Note that CSS3 as a unit doesn't exist. 'CSS3' is a collection of modules, some of which are in the Candidate recommendation state, some others are just early (concept) drafts. Those modules are all labeled with 'CSS' and 'level 3'. Support is not at all dependent on platform but on rendering-engine (browser). I seriously doubt Andy would make the claim that support is better on OS X than other OS. Modules one seriously can start using include the Selectors module [1], the border and backgrounds module [2] to name two that more wide support in various browsers; other modules have at least a partial implementation in various browsers. For a full list, see [3]. He also advocates NOT trying to make the presentation of a website look the same in all browsers, but to write to the limit of the CSS capabilities of each individual browser, and use things like conditional includes, media rules, and @import to control what CSS gets seen/used by which browser(s). Which is a philosophy I fully support. It is called progressive enhancement. Question the first: Is this a widely-accepted philosophy in the web-design community, and is it being widely adopted - and should it be? Why not use it, certainly on personal sites and even on commercial sites ? This can only help improve browser support. [1] http://www.w3.org/TR/css3-selectors/ [2] http://www.w3.org/TR/css3-background/ [3] http://www.w3.org/Style/CSS/current-work Philippe --- Philippe Wittenbergh http://l-c-n.com/ __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Transcendant web design and CSS3
On Sun, 7 Mar 2010 15:49:43 -0800, Thierry Koblentz
thierry.koble...@gmail.com wrote:
[Quoting me in ]
Question the first: Is this a widely-accepted philosophy in the
web-design community, and is it being widely adopted - and should it
be?
I think this is the right approach, but note that most of the time there is
no need to control what is sent to a particular browser as a property which
is not supported is simply ignored.
For example consider this:
.myBox {
border:1px solid #333;
-moz-border-radius:3px;
-webkit-border-radius: 3px;
border-radius: 3px;
}
This appears to be trying to make the page appear 'the same' (or at
least very similar) in all browsers, while using the advanced
capabilities that might be available. Mr Clarke is suggesting
otherwise; an example in the book shows, for example, the serving of a
completely black-and-white-and grey page when viewed with IE6, but full
color (and certain graphical accents are completely different) when
viewed with FireFox.
I understand that one cannot expect to see THE SAME THING in all
browsers, as though the screen was a printed page; nevertheless, the
philosophy that I learned when I was first starting web design (and the
use of CSS) was to try to avoid radical differences in the appearance
from browser to browser, or screen size to screen size. That's what
I've done with my website at http://www.freelancetraveller.com - but it
appears that Mr Clarke disagrees with this philosophy, embracing its
opposite, and THAT is what I am questioning.
Question the second: What is the current level of support for CSS3?
There are some interesting ideas in CSS3, which I would like to be able
to use - but I'd like to know that the support is there and relatively
stable before attempting to use it.
This is a great resource:
http://a.deveria.com/caniuse/
Thank you; this does indeed appear to be quite useful - and tells me
that CSS3 is not ready for prime time, and probably should not yet be
used as I'd like to use it.
--
Jeff Zeitlin, Editor
Freelance Traveller
The Electronic Fan-Supported
Traveller® Fanzine and Resource
edi...@freelancetraveller.com
http://www.freelancetraveller.com
http://come.to/freelancetraveller
http://freelancetraveller.downport.com/
®Traveller is a registered trademark of
Far Future Enterprises, 1977-2009. Use of
the trademark in this notice and in the
referenced materials is not intended to
infringe or devalue the trademark.
Freelance Traveller extends its thanks to the following
enterprises for hosting services:
CyberNET Web Hosting (http://www.cyberwebhosting.net)
The Traveller Downport (http://www.downport.com)
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Transcendant web design and CSS3
On Mon, 8 Mar 2010 09:11:25 +0900, Philippe Wittenbergh e...@l-c-n.com wrote: On Mar 8, 2010, at 8:21 AM, Jeff Zeitlin wrote: Mr Clarke is pushing CSS3 in this book, though he notes that (at the time the book was written) support for CSS3 was spotty at best even for the Mac (his preferred platform). Note that CSS3 as a unit doesn't exist. 'CSS3' is a collection of modules, some of which are in the Candidate recommendation state, some others are just early (concept) drafts. Those modules are all labeled with 'CSS' and 'level 3'. Support is not at all dependent on platform but on rendering-engine (browser). I seriously doubt Andy would make the claim that support is better on OS X than other OS. At the time the book was written, he essentially was, as the webkit engine was only available in Safari/Mac. Modules one seriously can start using include the Selectors module [1], the border and backgrounds module [2] to name two that more wide support in various browsers; other modules have at least a partial implementation in various browsers. For a full list, see [3]. Thank you for these links; they will clearly come in handy. He also advocates NOT trying to make the presentation of a website look the same in all browsers, but to write to the limit of the CSS capabilities of each individual browser, and use things like conditional includes, media rules, and @import to control what CSS gets seen/used by which browser(s). Which is a philosophy I fully support. It is called progressive enhancement. No. He specifically denigrates Progressive Enhancement, describing it as ...begins with less capable browsers such as Internet Explorer 6 and then uses CSS selectors to add functionality. His Transcendent CSS abandons the notion that a less-capable browser is the benchmark, and sets that benchmark squarely where it belongs today, with the CSS2.1 specification and those browsers that support it. It uses all the available CSS2.1 features, not to add visual enhancement, but to accomplish the best design for the most, standards-capable browsers. In other words, design for the MOST capable browser, and then don't try too hard to to support less-capable browser beyond making sure that it doesn't look completely like something I might not want to step in walking down the street. Or do try hard if you want to invest the time and effort - but basically, if Gecko can do it, and you like it, go for it, even if neither Webkit nor Trident support it. Or swap the engine names around as you see fit. [Side question for folks here that do a lot of design and testing: For a given engine and level, do you see differences in the way different browsers render the page? For example, do you see a difference between Lunascape-using-Trident and IE? Or Safari vs Google Chrome?] __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Transcendant web design and CSS3
Plus, I don't think the vast majority of website owners are going to permit the charges for the kind of time this would take, so while it would be worthwhile to try on one's own site, it's probably not best to effect this across all your sites in progress. Theresa On Mar 7, 2010, at 4:40 PM, Freelance Traveller wrote: This appears to be trying to make the page appear 'the same' (or at least very similar) in all browsers, while using the advanced capabilities that might be available. Mr Clarke is suggesting otherwise; an example in the book shows, for example, the serving of a completely black-and-white-and grey page when viewed with IE6, but full color (and certain graphical accents are completely different) when viewed with FireFox. I understand that one cannot expect to see THE SAME THING in all browsers, as though the screen was a printed page; nevertheless, the philosophy that I learned when I was first starting web design (and the use of CSS) was to try to avoid radical differences in the appearance from browser to browser, or screen size to screen size. That's what I've done with my website at http://www.freelancetraveller.com - but it appears that Mr Clarke disagrees with this philosophy, embracing its opposite, and THAT is what I am questioning. Thank you; this does indeed appear to be quite useful - and tells me that CSS3 is not ready for prime time, and probably should not yet be used as I'd like to use it. __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] freaking error
On this file [1] there are 5 images at the very bottom of the left column #one. In addition to the fact that they blink, which is going to put me in a locked-ward momentarily, there is an html and/or css error that escapes me. There should be 3 images in left column set flush left, and 2 images in the right column set flush right. Anyone able to pick up my error (s)? login: tl pass: tl1 [1] http://chelseacreekstudio.com/tl/tl_7.htm CSS: lines 150 through 160 embedded. Thanks, ~d -- desktop http://chelseacreekstudio.com/ mobile http://chelseacreekstudio.mobi/ __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Transcendant web design and CSS3
Theresa Mesa wrote: Plus, I don't think the vast majority of website owners are going to permit the charges for the kind of time this would take, so while it would be worthwhile to try on one's own site, it's probably not best to effect this across all your sites in progress. Theresa Web site owners are in the dark. They will possibly in the future regret their backward thinking and lack of foresight. It similar to supporting quirks mode in 2020. -- Alan http://css-class.com/ Armies Cannot Stop An Idea Whose Time Has Come. - Victor Hugo __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Transcendant web design and CSS3
Freelance Traveller wrote:
On Sun, 7 Mar 2010 15:49:43 -0800, Thierry Koblentz
thierry.koble...@gmail.com wrote:
[Quoting me in ]
Question the first: Is this a widely-accepted philosophy in the
web-design community, and is it being widely adopted - and should it
be?
I think this is the right approach, but note that most of the time there is
no need to control what is sent to a particular browser as a property which
is not supported is simply ignored.
For example consider this:
.myBox {
border:1px solid #333;
-moz-border-radius:3px;
-webkit-border-radius: 3px;
border-radius: 3px;
}
This appears to be trying to make the page appear 'the same' (or at
least very similar) in all browsers, while using the advanced
capabilities that might be available. Mr Clarke is suggesting
otherwise; an example in the book shows, for example, the serving of a
completely black-and-white-and grey page when viewed with IE6, but full
color (and certain graphical accents are completely different) when
viewed with FireFox.
You can still support IE6- but some authors just don't want to bother
understanding why IE6- has shocking CSS2.1 support or why a document
is rendered broken in IE6-. I agree with Andy Clarke by sending
IE6/Win un-styled pages but their is also that user agent IE5/Mac.
I understand that one cannot expect to see THE SAME THING in all
browsers, as though the screen was a printed page; nevertheless, the
philosophy that I learned when I was first starting web design (and the
use of CSS) was to try to avoid radical differences in the appearance
from browser to browser, or screen size to screen size. That's what
I've done with my website at http://www.freelancetraveller.com - but it
appears that Mr Clarke disagrees with this philosophy, embracing its
opposite, and THAT is what I am questioning.
I also disagree with that backwards philosophy. I attempt to suggest
of philosophy of styling a page with future support in mind. My own
test pages shows this philosophy.
Question the second: What is the current level of support for CSS3?
There are some interesting ideas in CSS3, which I would like to be able
to use - but I'd like to know that the support is there and relatively
stable before attempting to use it.
This is a great resource:
http://a.deveria.com/caniuse/
Thank you; this does indeed appear to be quite useful - and tells me
that CSS3 is not ready for prime time, and probably should not yet be
used as I'd like to use it.
I have been using CSS3 for over 2 years. IE9 will have support for
rounded corner so nested divs could be seeing their last days. Here is
a page of mine (style is basically from 2008) that uses CSS3 and give
some examples.
http://css-class.com/test/css/
--
Alan http://css-class.com/
Armies Cannot Stop An Idea Whose Time Has Come. - Victor Hugo
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] freaking error
On Mon, Mar 8, 2010 at 7:38 AM, David Laakso da...@chelseacreekstudio.com wrote: On this file [1] there are 5 images at the very bottom of the left column #one. In addition to the fact that they blink, which is going to put me in a locked-ward momentarily, there is an html and/or css error that escapes me. There should be 3 images in left column set flush left, and 2 images in the right column set flush right. Anyone able to pick up my error (s)? login: tl pass: tl1 [1] http://chelseacreekstudio.com/tl/tl_7.htm CSS: lines 150 through 160 embedded. Not sure to have understood exactly the problem. I see 5 images, _all in the left column_. Three are wrapped inside a left floated box (.three) and two in a right floated box (.four). The third one, srooks00.gif, does not appear flush left in spite of being in a left floated box. The reason is that the height of the second one (ssheerr_.gif) is smaller than the first one (58px versus 60px; height specified in the html as attribute of img), and a left float always prefers to stay higher than more to the left. Best, Bruno -- Bruno Fassino http://www.brunildo.org/test __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] IE8 bidi and hasLayout
On Sun, Mar 7, 2010 at 5:47 PM, Alan Gresley a...@css-class.com wrote: It appears that MS has hacked in bidirection (somewhat improved over IE7) by the use of *hasLayout*. http://css-class.com/test/bugs/ie/ie8-haslayout-bidi.htm Yes, I see the problem, very interesting! I just would say that direction sometimes makes a block a formatting context root (this is not necessarily related to hasLayout, which seems to have no more rendering effects in IE8, even if it still exists just as a dom / javascript property). Best, Bruno -- Bruno Fassino http://www.brunildo.org/test __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
