Re: [css-d] Site check
RE: Site check you requested on www.theheetproject.org.uk Hi Tim, This is a very nice looking site. Really excellent. I took a _very brief_ look in IE7 RC1, Firefox 1.5, Opera 9, LynxViewer and a number of other tools. A couple of suggestions for you to consider. 1) Source order: I prefer not to have the navigation at the start of the XHTML, and to let the real meat of the document come first. (Which you have done for some of the secondary content already.) Nicer for accessibility and possibly better for search engines. Shouldn't be tooo hard in this particular case to arrange this with positioning. 2) Conditional comments: Your IE-conditional comment if gte ie 5.5 is open ended. I'm not sure that this is necessary for IE7 (IE8?), it might or might not be, you probably have already looked into this. If not, I would suggest that you take a look into this anyway and try knocking it out for IE7. Certainly, it would be safer to limit it to IE5-6/Win unless there's some need for it now, and it probably is not good to continue to allow hacks to run on into future ever more compliant IE releases. Anyway, there's certainly no obvious problem _now_ at al - it looks very fine in IE7 RC1. 3) Links to same page. Just a personal thing, but I prefer to avoid nav links that point to the page you're already on, and which just cause a reload. Consider making the current entry just some text within the li. See what you think. I'm sure that when you get the real text in you won't have link text like "click here". 3) I doubt it's worth bothering with meta-keywords any more. See http://searchenginewatch.com/showPage.html?page=2165061 and http://www.searchengineguide.com/ball/006037.html but see http://www.seologic.com/faq/meta-keywords.php for a contrary opinion. Very attractive. Cecil Ward. __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] Long outstanding IE7 bug still unfixed in IE7 RC1 - CSS selector parsing, comment handling with attribute selectors - serves as an IE7 hack or filter
It seems IE7 RC1 still has an outstanding CSS parsing problem, which although reported a long time ago,never got fixed, and now could serve as a hack that forms the basis for an IE7-exclusion filter. See the test case I posted a good while ago at http://archivist.incutio.com/viewlist/css-discuss/72604 But please, no more CSS hacks. Best, Cecil Ward. __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] W3C CSS validator accepts garbage pseudo-class values
[Following on from my earlier post] The W3C CSS validator seems quite happy
to pass
:hovvverr {}
or
:garbage {}
or
:garbage:first-line {}
and plenty more such nonsense.
I have no idea why it seems quite happy with unknown
pseudo-class/pseudo-element names. (It after all gives an error on bad
property names, for example.)
This then is the reason then why it passes all kinds of junk like
element:first-line\:first-letter {}
because it treats this as a single long identifier, and doesn't mind that it
is unknown.
Am I missing something?
Cecil Ward.
__
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Syntax of pseudo-elements/pseudo-classes
Philippe, thanks for the link to the SelectOracle tool. Your understanding
tallies with mine.
Francky, my point was that I have my suspicions about the W3C CSS validator,
and find the various CSS grammars unhelpful, particularly on points such as
the distribution of comments, distribution of whitespace, order of parsing
phases and escaping.
So I wanted a sanity check on this.
The SelectOracle tool, the W3C validator and my own brain agree that #1 is
invalid
*\:first-line {}
So, "a colon may not be escaped". (If it is, it is seen as part of an
identifier, I suppose.)
Now the following nonsense
*:first-line\:hover {}
ought to fail surely, but for a different reason. This is my interpretation
of it. The escaped colon makes the entire thing "first-line\:hover" into a
single identifier, as if the colon didn't exist in a sense. So what we get
is a long, unrecognised pseudo-class name.
Cecil Ward.
__
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] Syntax of pseudo-elements/pseudo-classes
Are the following valid snippets of CSS?
1. *\:first-line {}
2. *:fist-line {}
3. *:garbage {}
4.someelement:garbage {}
5.*:first-child\:first-letter {}
Cecil Ward
__
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] IE7 build 5335 possible outstanding CSS parsing bug - comment handling with attribute selector
A question about the CSS specs and a bug report for IE7 build 5335.
IE7 build 5335 "fails" the test t1 in the test case below. I say "fails" in
the sense that I'm assuming that the consensus represented by the behaviour
shown by Firefox 1.5 and the current pre-release versions Opera 9 is assumed
to be correct.
Could someone tell me whether the test below is valid or fair?
That is, I am assuming that my reading of the unhelpful CSS 2/2.1 specs is
that comments are in a sense ignorable, in that they are not separators
equivalent to whitespace, so that a selector such as
*[lang]/**/[xmlns]
should be equivalent to *[lang][xmlns]
and not equivalent to
*[lang] [xmlns]
Is that correct?
Cecil Ward.
Test case follows:-
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
*[lang]/**/[xmlns] #t1 { font-style:italic; }
p/**/#t2{ font-style:italic;}
Should be italic.
Should be italic.
__
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] IE7 build 5335 (march 20 release) and listamatic's vertical lists
An update on IE7's progress, and styled vertical nav lists.
A month ago I had reported that the listamatic vertical list example at
http://css.maxdesign.com.au/listamatic/vertical13.htm
appeared broken in the earlier Feb build of IE7. (The earlier bug report is
at http://blogs.msdn.com/ie/archive/2006/01/31/520883.aspx )
This appeared to me be due to a bug in that build of IE7, maybe I was wrong.
Having retested this in IE7 build 5335 (the March 20 release) there is still
a problem. The vertical list on that page still renders incorrectly, with
large vertical gaps.
However this issue is demonstrably related to a bad CSS hack, which needs to
be changed. The hack is at:
#navcontainer>ul#navlist li a { width: auto; }
It turns out that knocking out that hack, as an experiment, happens to fix
the rendering here. Doing so equates to treating IE7 like IE6 in this
particular case.
Anyway, the hackery needs to be re-thought, and I don't have a proper fix
for this issue at hand. (I don't ever use in-CSS hacks, I always use
completely separate browser-specific CSS, delivered by CSS filters.)
Cecil Ward.
__
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] IE7 hovers and a IE vertical list bug?
> If you write the 's without line breaks between them, the space disappears. Searching around, there are a fair number of these whitespace-in-HTML-related bugs in browsers' CSS handling. I myself took the decision to postprocess my (X)HTML in order to be able to manage this. I do already use the HTML Tidy tool (http://www.w3.org/People/Raggett/tidy/), as an HTML postprocessor. Tidy is supposed to help avoid some of these whitespace browser bug issues, but unfortunately current versions of Tidy (as at early 2006) actually _introduce_ this kind of whitespace problem, and do so even if you do not choose Tidy's indent/pretty-print output option. So as a complete and lasting cure, I wrote a quick and dirty postprocessor tool, which I run to completely strip all newlines from the HTML. If anyone would like a copy of this tiny little newline stripper tool, just ask, e: cecilcecilward.com. [The tool is indeed quick and dirty, a javascript program (Microsoft JScript dialect) running as a command line tool under Windows CSCRIPT, so I'm afraid this limits it to recent Microsoft o/ses. Mac OSX anyone? The current version also requires that your HTML sources be either in UTF-8 or in some single-byte character encoding such as ISO-8859-1, say. Character encodings such as UTF-16 are not (yet) supported.] Regards, Cecil Ward. __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] CSS validators?
I'm interested in either getting hold of a standalone tool that validates CSS files, or in building my own. I'd like to automate CSS validation as part of a build process, so I'm not interested in interactive or IDE-type tools, and web-based services such as the W3C's validator are out of question. Does anyone have any experience with such tools? Cecil Ward. __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Using IE7b2 for testing
> is it wiser to wait worrying about it until IE7 is actually released when I can tell whether the issues are there to stay or no? See http://meyerweb.com/eric/thoughts/2006/02/03/charting-ie7b2/#comment-14367 Yes and no. There's no point doing any rework or expending much effort on a release that is so early and so broken in certain areas. But don't wait until the final release, keep an eye on the later, more complete and more dependable 'real' betas. Cecil Ward. __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
