[WSG] skiplink messes up tabindex order IE6
Hello list, I just implemented a skiplink but it messes up the tabindex order of my nav in IE6. Anybody has a clue what could be the culprit? http://www.dzinelabs.com/sandbox/GrupoMP/Pages/home1.html Css embedded. The relevant css is the last part of the styles. What's going on is the following: i need to tab 5 times to get to the link with tabindex 2. Upon tab number 10 i get to tabindex 6. Tab number 10 brings me to the skiplink. -- Regards, Luc _ http://www.dzinelabs.com Using the best e-mail client: The Bat! version 4.2.6 with Windows XP (build 2600), version 5.1 Service Pack 3 and using the best browser: Opera. "I’m all for bringing back the birch, but only between consenting adults." - Gore Vidal (1925) - US author *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Checking CSS3 Support [ or CSS3 Border Background]
On Aug 9, 2009, at 4:31 PM, Bushidodeep wrote: Hi, As usual, all the replies to my post have been valuable, providing much to think about. Does a JS/DOM script exist for checking CSS3 support across user-agents? http://www.css3.info/selectors-test/ tee *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
[WSG] Checking CSS3 Support [ or CSS3 Border Background]
Hi, As usual, all the replies to my post have been valuable, providing much to think about. Does a JS/DOM script exist for checking CSS3 support across user-agents? C On Aug 9, 2009, at 3:22 PM, Keryx Web wrote: On 2009-08-09 12:48, Stuart Foulstone wrote: The hr element represents a paragraph-level thematic break, e.g. a scene change in a story, or a transition to another topic within a section of a reference book. Correct, but rarely useful. The only indication given to users is visual. I do not think AT-technologies picks it up. So the decision is circumstantial, sometime you use hr, and sometimes use CSS 3 border background property. I've not seen a case in a really long while where an hr would be useful, except for debugging. deprecated in XHTML and the correct mark-up is to use a header which helps to help define that relationship. No, it is not. But it is better avoided, as said by many in this thread. -- Keryx Web (Lars Gunther) http://keryx.se/ http://twitter.com/itpastorn/ http://itpastorn.blogspot.com/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] or CSS3 Border Background
On 2009-08-09 12:48, Stuart Foulstone wrote: The hr element represents a paragraph-level thematic break, e.g. a scene change in a story, or a transition to another topic within a section of a reference book. Correct, but rarely useful. The only indication given to users is visual. I do not think AT-technologies picks it up. So the decision is circumstantial, sometime you use hr, and sometimes use CSS 3 border background property. I've not seen a case in a really long while where an hr would be useful, except for debugging. deprecated in XHTML and the correct mark-up is to use a header which helps to help define that relationship. No, it is not. But it is better avoided, as said by many in this thread. -- Keryx Web (Lars Gunther) http://keryx.se/ http://twitter.com/itpastorn/ http://itpastorn.blogspot.com/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
[WSG] Out of Office AutoReply: WSG Digest
Hi, Thanks for your mail. I am on holiday until the 24th August, and will only be accessing my e-mail once in a while. If your mail requires an urgent response and relates to FourHats, please email si...@fourhats.com for technical support, accou...@fourhats.com for accounts, or either c...@fourhats.com or si...@fourhats.com for anything else. Best regards. Jake. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] or CSS3 Border Background
Sorry, I missed this bit when I last responded. On 9 Aug 2009, at 10:38, tee wrote: Which specification deprecated it? This is what I learned: All "presentation attributes" of the hr element were deprecated in HTML 4.01 Deprecating some attributes on an element does not deprecate the element itself. -- David Dorward http://dorward.me.uk *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] or CSS3 Border Background
On 9 Aug 2009, at 10:38, tee wrote: On Aug 9, 2009, at 1:36 AM, David Dorward wrote: On 9 Aug 2009, at 03:53, tee wrote: Then my question, what about those who prefer to stick with XHTML? By "Stick with XHTML" do you mean "not to move to an unstable, draft markup language"? Plenty of people are happily writing HTML 4.01 and avoiding the pain of Appendix C. But isn't it going to have XHTML2 as well? Given that the XHTML working group is being wound up — it seems unlikely. Whatever 'it' is. Things HTML5 does not do: • Does not favor XML facilities (what does this mean? What impact will it have for sites that were built in XHTML strict and CMS that parse XML (not just the RSS feed)? ) Rubbish. It has an XML serialization. • Does not avoid scripting What does this mean? Scripting has its place. • Does not consider integration with the SemWeb a priority (and what does this mean? Is "SemWeb" semantic web? Both Yahoo and Google adapted Semantic Web, what impact will it have for SEO?) The relationships to RDFa and other semweb technologies are some of the more unstable parts of the HTML 5 draft. So, people like me who are in the web development, but our well- being are on the mercy of you pioneers, HTML5, XHTML2.0 authors and W3C's If you don't like it. Participate in the process. http://www.w3.org/html/wg/ -- David Dorward http://dorward.me.uk *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] or CSS3 Border Background
On Sun, August 9, 2009 3:53 am, tee wrote: > > ... > However, seeing that HTML 5 has given hr tag a new purpose: > http://dev.w3.org/html5/spec/Overview.html#the-hr-element > http://dev.w3.org/html5/spec/Overview.html#flow-content-0 > > quote: > The hr element represents a paragraph-level thematic break, e.g. a > scene change in a story, or a transition to another topic within a > section of a reference book. > > > So the decision is circumstantial, sometime you use hr, and > sometimes use CSS 3 border background property. > > Then my question, what about those who prefer to stick with XHTML? The > hr tag is deprecated. > > In gassho, > tee When the tag is not used as a purely visual element (which is bad practice), it separates two distinct pieces of content but gives no information about their relationship. deprecated in XHTML and the correct mark-up is to use a header which helps to help define that relationship. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] or CSS3 Border Background
On Aug 9, 2009, at 1:36 AM, David Dorward wrote: On 9 Aug 2009, at 03:53, tee wrote: Then my question, what about those who prefer to stick with XHTML? By "Stick with XHTML" do you mean "not to move to an unstable, draft markup language"? Plenty of people are happily writing HTML 4.01 and avoiding the pain of Appendix C. But isn't it going to have XHTML2 as well? I am not a pioneer but a over-work, over exhausted web worker who barely keep up with latest technology, so I do not study HTML5 nor XHTML2 like many of you do. I do pay attention when I see articles regarding HTML 5 surface in many blog-dom in the past month. There are CMS that rely on XML (one I know and work on every day is the Magento) and this caught my eyes sometimes ago: Things HTML5 does not do: • Does not favor XML facilities (what does this mean? What impact will it have for sites that were built in XHTML strict and CMS that parse XML (not just the RSS feed)? ) • Does not avoid scripting • Does not consider integration with the SemWeb a priority (and what does this mean? Is "SemWeb" semantic web? Both Yahoo and Google adapted Semantic Web, what impact will it have for SEO?) • No arbitrary namespaces. Things XHTML2 does not do • Does not support existing contention the same way that HTML5 does • Does not precisely define UA behavior • Does not handle errors non-draconically (uses "catch fire and fail" error handling) • No arbitrary namespaces. So, people like me who are in the web development, but our well-being are on the mercy of you pioneers, HTML5, XHTML2.0 authors and W3C's , I have had this question since the first time I read about HTML5 draft years ago from this list, that there had long been battles between html 4.0 strict and XHTML strict, none are perfect and those who favored XHTML led some believe this is the future of web standards and I stick to it and I am not alone. Since none are perfect, now you guys were moving forward, working hard to bringing a whole new standards to us, why can't the HTML5 and XHTML2.0 working group just give us ONE standards? Thus far the impression I got from many articles I have read, is that HTML5 will be the standards, is better. Is that right? Sorry, I am not being sarcastic here. And I don't suppose this is a Mac Vs PC kind of choice that you pick what works best for you, or choose to use Opera or Google Chrome or Firefox. The hr tag is deprecated. Which specification deprecated it? This is what I learned: All "presentation attributes" of the hr element were deprecated in HTML 4.01, and are not supported in XHTML 1.0 Strict DTD. In gassho, tee *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] or CSS3 Border Background
After reading the following article, I ask which is more semantic, using the
> element with a background or using the CSS3 border background
> property?
Well... markup has semantics/semantic meaning, CSS is style applied over the
top but is not part of the document's content. Applying the graphic with CSS
only means you are saying it's purely visual and not part of the content at
all... and I don't think that's what you really intend.
So if you are communicating a break in content (which is the semantically
meaningful concept), include the even if you then hide it and display
a border when CSS is applied. On my blog I do just that, with
and
.hidden {
position: absolute;
left: -5000px;
width: 4000px;
overflow: hidden;
}
I should really change the class to "assistive" as it's not actually
"hidden" from everybody, but that's a finer point. Anyway, with the HRs
hidden from view with CSS I then have a design with very clear breaks in the
content, which is a visual representation of the underlying semantics.
cheers,
Ben
--
---
Re: [WSG] or CSS3 Border Background
On 9 Aug 2009, at 03:53, tee wrote: Then my question, what about those who prefer to stick with XHTML? By "Stick with XHTML" do you mean "not to move to an unstable, draft markup language"? Plenty of people are happily writing HTML 4.01 and avoiding the pain of Appendix C. The hr tag is deprecated. Which specification deprecated it? -- David Dorward http://dorward.me.uk *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
