Looking at the demo page, it looks like authors would be better using a
faux-columns technique which would also remove the need for polling.
Or is there a better reason to go the JS route?
--
Thierry
On Dec 21, 2011, at 1:02 PM, Al Sparber wrote:
Happy Holidays from PVII
Save time this
I think my only option is to generate an image for the banner
using the right font (or is there a better option?).
What is the current best practice for having an accessible text
banner, while showing the image based banner?
Are we still using the trick of shifting the text off the side
Hi Tee,
#mini-cart {position:absolute; width:300px; overflow: hidden}
I didn't follow the whole thread, but seeing the above I have a suggestion:
Try an explicit left value (i.e. left:0;) as IE is known to need that in
many cases.
--
Regards,
Thierry
@thierrykoblentz
www.tjkdesign.com |
I see this unit being used with margin for example, in Mozilla and WebKit
styles sheets, but I can't find any reference to it.
Looks like it is mostly use to declare vertical values (top, bottom, before,
after).
Any clue?
Thanks
--
Regards,
Thierry
@thierrykoblentz
www.tjkdesign.com |
This question has come up on CSS discuss in the past.
http://archivist.incutio.com/viewlist/css-discuss/104705
One answer:
I believe qem stands for quirky em and is a proprietary Webkit
syntax
used to refer to a margin which can be collapsed when the page is in
quirks mode.
Thanks a lot
http://www.surveymonkey.com/s/SNMWNW2
Give it a shot!
--
Regards,
Thierry
@thierrykoblentz
www.tjkdesign.com | www.ez-css.org | www.css-101.org
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
When it comes to search engine optimisation,
Stop. Build sites for people, not robots. Search engines are optimising
to find the best sites for people, aim for the same target as they are.
+1
--
Regards,
Thierry
@thierrykoblentz
www.tjkdesign.com | www.ez-css.org | www.css-101.org
Hi Emily,
Thank you for your reply as well. I will check into
http://webdesign-L.com/.
Before you post to that list, make sure to check this page:
http://webdesign-l.com/policies/ and obey the *rules*
Regarding how-to keep navigation state, you could try this:
Screen readers doesn't process javascript, so no AJAX requests will be made.
I don't think so.
There are a couple of good article from Gez Lemon and Steve Faulkner about Ajax
and SRs:
http://juicystudio.com/article/making-ajax-work-with-screen-readers.php
Thanks for the answers. I think the media queries could be the way to go.
I'll give it a try.
Did you try to download the SDKs?
I installed the IOS Simulator and it works well (runs faster though).
--
Regards,
Thierry
@thierrykoblentz
www.tjkdesign.com | www.ez-css.org | www.css-101.org
Here's the page in question:
http://www.koisis.com/.clients/vascos/dev/facilities.htm
Anchor tag (View Gallery) is in the div with the Image to Come
image.
If you look at this link in FF (et. al) you'll see it's positioned
correctly.
Now switch to IE 8 (probably ie 7 as well) and
I don't know if many people have adopted this approach yet, but I wrote
something about the potential issues:
http://www.css-101.org/articles/thoughts_on_the_new_html_elements_and_surrog
ate_divs/
Any and all feedback welcome.
--
Regards,
Thierry
@thierrykoblentz
www.tjkdesign.com |
An alternative to get the first dd in a dl:
:first-child + dd { ... }
That would not be a sure thing as this could match a dt too
--
Regards,
Thierry
@thierrykoblentz
www.tjkdesign.com | www.ez-css.org | www.css-101.org
An alternative to get the first dd in a dl:
:first-child + dd { ... }
That would not be a sure thing as this could match a dt too
Scratch that, I didn't have my coffee yet ;)
--
Regards,
Thierry
@thierrykoblentz
www.tjkdesign.com | www.ez-css.org | www.css-101.org
The :first-child pseudo-class represents an element that is the first
child of some other element..
I have often used li:first-child or li a:first child in different
section of a page, why is that I can get the first-child in, say,
#hdr li:first-child
.sidebox li:first-child (and it
HI Nancy,
We have a situation where there is a checkbox within a loop, there
could be 1 to as many as 50 instances depending on the results of a
query.
The id is checkbox and and is needed to remain the same for
dynamic reasons according to the engineer.
If they need something that
With Collapsible, it's largely a UI/Design choice, structurally, the
content in it is part of the main content, it's just a simple show/hide
that makes good use of space, and apart from button that you
recommended, a heading can be served as a trigger too depending on the
content (for the
Hi Tee,
Please take a look at this example. The first example is keyboard
accessible however I am also concern with the empty link that may
create extra noise for screen reader, e.g if every single page has a
popup, it will have two empty links, one is the popup trigger and the
other the
You can use it, but will anyone benefit from it? Assistive technologies
don't support much, if any, of the new semantics. I don't know if search
engines and other users of programmatic access to websites are currently
able to make use of HTML5 markup, but I have not seen anything to indicate
that
At the moment, HTML5 doesn't really bring a significant benefit, but
that will change (in years rather than months).
I beg to differ. I believe there are a lot of great stuff that we can start
using today (mostly related to form controls).
See http://diveintohtml5.org/forms.html and this one
Hi Steve,
Yes, here's one we worked on -
http://htmltools.moneymadeclear.org.uk/mortgage-calculator/index.aspx
What about using role=alertdialog on that container?
http://www.w3.org/TR/wai-aria-practices/#chobet
--
Regards,
Thierry
@thierrykoblentz
www.tjkdesign.com | www.ez-css.org |
These two essentially are the same. I am assuming the menu is
controlled by a javascript, best practise is to use the absolute
positioning to control submenu and use the toogle or mouseover to
trigger the sub-level.
I'm not sure this is considered best practice as keyboard users would have
These come to mind???
The appropriate w3c list, and...
http://www.sitepoint.com/forums/
http://csscreator.com/
http://bytes.com/
Thanks David, but I'm not a big fan of fora (I prefer mailing lists).
Even though a forum like sitepoint has great threads (i.e. Test Your CSS
Skills).
Check this
Hi all,
Besides the CSS-D list, which CSS lists would you recommend subscribing to?
Thanks,
--
Regards,
Thierry
@thierrykoblentz
www.tjkdesign.com | www.ez-css.org | www.css-101.org
***
List Guidelines:
Hi David,
It appears to be the existence of hasLayout on the .vcalendar that
causes the problem (due to it being floated...)
I don't think this is the issue per se. Imho, the problem is that this float
is width-less.
Give it with a width and things should work the way you want.
--
Regards,
http://www.css-101.org
Happy New Year!
Bonne Année!
--
Regards,
Thierry
@thierrykoblentz
www.tjkdesign.com | www.ez-css.org | www.css-101.org
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe:
@Diego: Smartphones are not the best device to use here since the idea behind
the demo pages is to allow people to edit/tweak CSS declarations via their
favorite dev tool. The goal is to make people get their hands under the hood to
do their own investigation - to find out what the simplest
Using IE conditional comments on the html tag, you can target each version
of IE.
You can does not mean you should...
In a comment [1] on forabeautifulweb, Molly Holzschlag says:
Please, please dont design for browsers.
[1]
Personally I think it is reasonable to take this approach, given the
age
of IE6 and its declining market share. However I would be interested in
the attitude of other developers.
Imho, we should take care of any layout issue, but not try to get fancy
effects via extra markup, images, filters,
The reason for this is twofold though: firstly, you want to coax people off
of IE6.
I don't think that's our job...
--
Regards,
Thierry
www.tjkdesign.com | www.ez-css.org | @thierrykoblentz
***
List Guidelines:
The reason for this is twofold though: firstly, you want to coax
people off of IE6.
I don't think that's our job...
Who better? Wouldn't you rather IE6/7 disappear sooner than later? You
enjoy
the extra effort the too many years of its massive non-conformity
causes?
Most people who
This article might also help:
http://www.alistapart.com/articles/spam/
I'm not sure about that. It is more than *8* years old...
--
Regards,
Thierry
www.tjkdesign.com | www.ez-css.org | @thierrykoblentz
***
List
Here is a link illustrating what I mean:
http://thinkplan.org/menupersist.jpg
What are peoples' thoughts on this kind of menu? I'm told that IE 6
doesn't support this kind of menu...IIRC, it involves
position: fixed;
How key is IE 6, and are people simply not going with this kind
http://203.193.216.214/
I have an issue with this menu it works fine but the client has asked
when you hover over
top menu that the sub menu becomes visible and the stays there until
you
hover over than
part of the top menu. If I was to move the mouse anywhere on the screen
the menu sub
Understandable; however, with the change in HTML5 from Definition Lists
to Description lists, would it not be more semantically valuable to
mark forms up using dt and dd, for labels and inputs, providing the
document with a more solid structure? As stated, my concern with this
is the lack of
Any thoughts on which we ought to be using, and what information
ought to be up at top of an HTML page, along with !DOCTYPE, etc?
I'd go with !DOCTYPE html with nothing above that
--
Regards,
Thierry
www.tjkdesign.com | www.ez-css.org | @thierrykoblentz
snip
On the second pahe I've checked
(http://www.projectseven.com/products/menusystems/pmm2/index.htm), I
found
these:
!--[if IE 7]
link href=/06_includes/ie7.css rel=stylesheet type=text/css
![endif]--
!--[if IE 6] link href=/06_includes/ie6.css rel=stylesheet
type=text/css
How, without using conditional comments at all, do I target IE
6,7, and 8
I was asking how I'd be able to target all three *without* any
CCs.
Using the basic filters you could go this route:
http://tjkdesign.com/lab/ie-filters.asp
For version 9+, nothing's sure ;-)
--
Regards,
Thierry
Thank you, Georg. Your valuable comments in that file actually
convinced
me to stay with the Paul Irish CCs method. It just seems safer, as
well as relatively easy to understand. After all, this:
.ie8 .hacked-element {...}
seems to me clearer than
@media all {
html:lang(en)
goes against the separation of the three layers
No it doesn't, it's purely presentational.
No better or worse than li class=last
imho, CCs have nothing to do with the presentational layer, they are part of
the structural layer and they are junk markup if you ask me :)
--
Regards,
Thierry
It must've come from that article, it looks vaguely familiar.
Personally I saw it as a furtherance to the hasJS technique.
My perspective was to remove separate style sheets, and obscure hacks, purely
to simplify editing exactly as Paul Irish's article states.
Without using * html and
This rule works
a[href^=http]
Problem is almost every CMS system uses absolute url for internal link,
this makes it impossible to target just the external link without the
content editor having to add a class to it.
If you deal with absolute paths, you should be able to match internal
On Behalf Of Al Sparber
From: Thierry Koblentz thierry.koble...@gmail.com
What is the solution you're talking about?
That link you posted does not tell us much about your own
simplistic,
unsophisticated way, nor what is your different view of menu
Accessibility.
It must be so
Probably. I think there is a faction in the accessibility community
that believes a web page menu should work like a desktop
application or OS menu. The problem is that web surfing civilians who
use the keyboard are accustomed to the tab key (or equiv) and
not the arrow keys for navigating a
Is this expected behavior or the support is still lacking?
I have this declared in CSS for HTML5 required attributed:
input type=email name=email id=email required
[required]{background-color:#E0}
input:focus, texture:focus
{background: #464646;color: #fff;border-color:
Hi Tee,
I thought this is suffice but then I am not sure as these HTML5 tags
are still too new for me.
section id=articles
article
h2.../h2
p.../p
/article
article
h2.../h2
p.../p
/article
/section
What about something like this?
ol id=articles
li
ol id=articles
li
article
header
h1a href=#Article Title/a/h1
/header
pLorem ipsum dolor sit amet, .../p
/article
/li
li
article
header
h1a href=#Article Title/a/h1
/header
pgiat nulla
/ is not necessary to close the meta tag.
meta charset=utf-8
Maybe this solve the problem.
Imho, the / should make no difference, I believe the problem is that this
meta is too far down in the markup.
The OP should try to put that meta right after head
--
Regards,
Thierry
I rather liked the conditionals around the body. What's not to like?
Imho, it goes against the separation of structure and presentation (plus it
messes up with the cascade), but I can understand why they are doing this.
Since most people strongly believe that CSS validation is a must, they have
Regarding performance, using a class may be a better choice:
https://developer.mozilla.org/en/writing_efficient_css
Interesting article. I wonder if it is still true -- the last update
was 2000 for that page.
2000 is the date for when the original article
At the very basic level, the article exemplifies
h1[rel=external]{color :
red;} used with the html:
h1 rel=externalAttribute Equals/h1
As others have said, this is an invalid use of rel. We could change
his example from:
h2 id=first-title class=magical rel=friendDavid Walsh/h2
As a follow-up to my original email, the following methods have been
very well designed from the accessibility point of view:
http://juicystudio.com/article/ecmascriptmenu.php
http://www.456bereastreet.com/archive/200705/accessible_expanding_and_c
o
llapsing_menu/
A further example
Hi Mathew,
http://tjkdesign.com/articles/keyboard_friendly_dropdown_menu/EK.asp
I have a bug report... tested against FF 3.6.4 and IE6 (no bug under
Chrome 5.0.376)
Steps to reproduce:
- click on background
- tab to focus first menu item
- hit enter to display sub-items
- tab through to
Try this for CSS menus with keyboard support:
http://carroll.org.uk/sandbox/suckerfish/bones2.html
This menu may be accessible, but is it usable?
Unless I am missing something, keyboard users need to go through *every
single link* in the menu to reach the last item :-(
I have these two:
Hi Mike,
Sorry to say this but the keyboard friendly version:
http://tjkdesign.com/articles/keyboard_friendly_dropdown_menu/EK.asp
Only fires, via keyboard, on Articles E-K in IEv8 or Firefox.
This is by design. Keyboard users could not reach these pages if they were
not focusable at least
Hi Grant,
I'm trying to avoid use of Javascript due to accessibility concerns.
There is no problem with using a javascript powered menu as long as that menu
is accessible with javascript off.
As a side note, pure CSS menus usually come with usability issues.
--
Regards,
Thierry
I stated earlier that after I got help on my previous IE6 problem that my
mainContent
div was shifted over to the left in Firefox.
http://www.jasonbyer.com/dev/new/
1. remove display:inline from #mainContent
2. remove the left margin on the div with no ID (the one that follows
#ddtopmenubar)
Ive been racking my brain trying to solve a CSS problem and I was hoping
somebody here can point me in the right direction. Im developing a site
that has to work in all modern browsers and IE 6. Here is the link to a
sample page:
http://www.jasonbyer.com/dev/new/
The problem that Im having
To concur with Thierry, the float on #mainContent appears unnecessary
on this page. Give it a margin, or padding, to push the content off
the left bar and you should be good to go.
These two containers are siblings, so if the OP uses padding or margin to
push the content off the left bar he
I'm taking care of Marvin, please do not reply to this thread
Thanks
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On
Behalf Of Marvin Hunkin
Sent: Tuesday, April 20, 2010 12:05 PM
To: wsg@webstandardsgroup.org
Subject: [WSG] recovering html and web projects
Sorry I wasn't clear. Does NVDA support everything that a paid
program such as JAWs supports?
That I couldn't tell you, but what I can say is that NVDA is a solid SR,
with great ARIA support, though
I believe it works better on Firefox than IE (re: change of content a la
Ajax).
As a side
Included amongst the inventions was Screen Reader software for
Windows, that was not only programmed by two blind computer users, is
licensed open source and thus freely available. It is called NVDA.
We use it for testing. It's very light and simple to use and you can't beat
the price :)
As a
I have run in to what seems to be an IE8 bug - IE8 doesn't respond to
internal links
(as in, same page links) on a demo site I'm working onyet IE6 and IE7 do!
eg.
a id=top name=top/a
ul
liblah blah blah/li
liblah blah blah/li
/ul
a href=#topback to top/a
I tried Googling and
I am working on a project that uses JSF with Richfaces and Ajax4jsf.
All the pages were developed using IE7.0 and they appear properly on it.
The same page is rendered a bit differently on the other browsers such as
Firefox,
Chrome. But the discrepancy is only w.r.t to the borders that are
Just wondering, is it possible to use the nth-child in CSS2 to target
the last 2 items of an unordered list?
I know you can do nth-last-child, but I wanted to target the last TWO
list items. Is this possible?
I believe this is CSS*3*, so support is not that great
--
Regards,
Thierry
Can anyone guess why the columns overlap?
http://freemealcenter.com
The first thing I'd try is to remove the float declaration on the fixed
element
--
Regards,
Thierry
www.tjkdesign.com | www.ez-css.org
***
List
Add an extra div within left_column, and declare the position:fixed
in the new div instead.
Or, since you already have an extra div, add this to screen.css:
.left_column { width: 220px; float: left; }
.left_column .column_cushion { width: 180px; position: fixed; }
I don't think there
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Jody Tate
Sent: Wednesday, February 10, 2010 2:05 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] the mysteries of overflow: hidden
Exactly. The magic confounds me.
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Dani Iswara
Sent: Saturday, February 06, 2010 6:26 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] FINAL VERSION OF MY SITE
Marvin,
For the access keys and title attributes, I do agree with Thierry. I
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Micky Hulse
Sent: Friday, February 05, 2010 9:54 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Progressive Enhancement
Hi,
Does anyone have any good resources for current progressive
enhancement
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Marvin Hunkin
Sent: Wednesday, February 03, 2010 2:47 PM
To: WSG@WEBSTANDARDSGROUP.ORG
Subject: [WSG] FINAL VERSION OF MY SITE
HI.
CAN SOME ONE TAKE A FINAL LOOK AT THIS SITE.
AND GOT 2 FONTS.
ONE
-moz is a vendor prefix (not CSS3)
--
Regards,
Thierry | www.tjkdesign.com
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On
Behalf Of Daniel Anderson
Sent: Wednesday, February 03, 2010 3:12 PM
To: wsg
Subject: [WSG] CSS Validation Error
When I am
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Karl Lurman
Sent: Wednesday, February 03, 2010 4:15 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] FINAL VERSION OF MY SITE
For your named anchor tags (a name=Marvin/a, they don't have to
be inside
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Stuart Foulstone
Sent: Wednesday, February 03, 2010 4:55 PM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] FINAL VERSION OF MY SITE
Hi Marvin,
On Wed, February 3, 2010 11:50 pm, Webb, KerryA wrote:
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Karl Lurman
Sent: Wednesday, February 03, 2010 5:22 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] FINAL VERSION OF MY SITE
Fwiw, I don't agree about accesskeys [1].
The article on your site seems
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Joshua Street
Sent: Wednesday, February 03, 2010 5:53 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] FINAL VERSION OF MY SITE
On Thu, Feb 4, 2010 at 10:41 AM, Paul Novitski
p...@juniperwebcraft.com
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Joshua Street
Sent: Wednesday, February 03, 2010 5:59 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] CSS Validation Error
On Thu, Feb 4, 2010 at 10:23 AM, Thierry Koblentz
thierry.koble...@gmail.com
different names for the rules, watch out for
that.
Theoretically, when a browser supports border-radius, it should switch from
its vendor specific rule to the standard rule.
Cheers
James
On Thu, Feb 4, 2010 at 10:23 AM, Thierry Koblentz
thierry.koble...@gmail.com wrote:
-moz is a vendor prefix
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Russ Weakley
Sent: Sunday, January 31, 2010 7:52 PM
To: wsg@webstandardsgroup.org
Subject: [WSG] Assistance with flash example sites
Hi people,
A colleague has just asked me for some examples of Flash
-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Marvin Hunkin
Sent: Monday, February 01, 2010 8:29 PM
To: wsg@webstandardsgroup.org
Subject: [WSG] fonts
hi.
i have verdana.
and it reads the name.
but only have got Arial
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Jason Grant
Sent: Sunday, January 31, 2010 1:06 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Accessibility does not matter!
@Matthew Pennell
You are confused with the 'broken wrist' issue. If I have
-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Jason Grant
Sent: Sunday, January 31, 2010 2:40 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Accessibility does not matter!
@Thierry
I think keyboard accessibility is
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Andrew Stewart
Sent: Sunday, January 31, 2010 2:51 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Accessibility does not matter!
Accessibility does matter, but I do think that many people on this
list
Sent: Sunday, January 31, 2010 3:46 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Accessibility does not matter!
Sorry to ask again, but please explain how the site could be made
accessible whilst maintaining the same ease of use?
The same ease of use?!
Drop the mouse and give it a
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Jason Grant
Sent: Sunday, January 31, 2010 4:24 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Accessibility does not matter!
@Thierry
Why does Google not care about accessibility? Do they believe in
On Behalf Of Patrick H. Lauke
Sent: Saturday, January 30, 2010 10:22 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Accessibility does not matter!
@Oliver Boermans IE6 / Intranets reply. Today we make a decision to
use JQuery as a framework for AJAX/JS. In two year JQuery gets
inaccessible and just wait until an employee with disabilities gets
hired, then redo it all?
Also, an employee with no disability today could have one tomorrow.
@Thierry Koblentz
'Could' is not something we should be developing for. We need to know
who we are developing for,
As I suggested
If you are looking for a simple search form (i.e. the input box into
which user enters a search term followed by 'Search' submit button)
you should be using something like this.
label for=sSearch/label
input type=text name=s id=s /
input type=submit value=Search class=primary /
You do
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Oliver Boermans
Sent: Saturday, January 30, 2010 8:21 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Minimal forms or marking up a search field
On 31 January 2010 13:45, Thierry Koblentz thierry.koble
Comments and suggestions on this site appreciated.
markup
http://chelseacreekstudio.com/mhr/
css
http://chelseacreekstudio.com/mhr/css/style.css
Hi David,
Minor things: I think the h1 looks small and that there is not enough
padding around the text in the menu. I think more padding would
I have one question I can't seem to find and answer to
below is all my css in a document I have created. It is xhtml
transitional. My document works fine except when I
add float:left; to my content div. It will not stay in the
wrapper. I know that it must be a simple answer. I have tried
Wow That work but why?
http://tjkdesign.com/articles/clearing-floats_and_block-formatting_context.a
sp
--
Regards,
Thierry | www.tjkdesign.com
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Hi Marvin,
You have br elements that are children of the list.
You need to remove these from there. You cannot have anything between List
Items (LI)
Start by fixing this and then revalidate.
--
Regards,
Thierry | www.tjkdesign.com
-Original Message-
From:
According to spec, it has no inheritence but it does in both browsers.
I changed it to li instead of li a, the screen shot taken is from li.
#element li{ text-shadow: 2px 2px 2px #000;}
http://picasaweb.google.com/weblist99/UntitledAlbum
Hi Tee,
Inheritance does not come into play here.
Also, please try our Opera Web Standards Curriculum section 27 entitled CSS
basics,
written and contributed by Christian Heilmann.
Here is the hyperlink to it: http://dev.opera.com/articles/view/27-css-basics/
There are a bunch of typos in there.
- Extra semi-colons,
- The :first-line and
On Fri, Jan 15, 2010 at 7:03 AM, Chris F.A. Johnson
ch...@cfajohnson.com wrote:
Every other discussion group I participate in regards clagnut
with derision.
There is no good reason for anything other than font-size: 100%.
That's not an explanation. ALA published a follow-up by Richard
In the example you provided, I'd do this:
1) move zoom: 1 to your IE6 rule (and to IE7 rule if necessary)
2) place the IE6 and IE7 rules in an IE ONLY sheet
3) use a conditional comment to call the IE sheet
Would that work? If so, please explain your reasons for not doing so.
Here are
Nick
Zoom:1 is not bad enough to warrant a conditional comment and separate style
sheet.
It's a valid rule that basically says show the screen at 100%. A user style
sheet
can still over-ride this rule. It's an easy way to add hasLayout without
causing
other issues.
This is what
Hi David,
On 1/13/10 12:24 PM, Thierry Koblentz wrote:
Nick Zoom:1 is not bad enough to warrant a conditional comment and
separate style sheet. It's a valid rule that basically says show
the screen at 100%. A user style sheet can still over-ride this
rule. It's an easy way to add hasLayout
Hi David,
(shameless plug)
http://tjkdesign.com/articles/Pure_CSS_Dropdown_Menus.asp
Fwiw, I've used it without issue (other than my own, of course). Nice
stuff, me /thimk/...
Thanks for the feedback
--
Regards,
Thierry | www.tjkdesign.com
1 - 100 of 543 matches
Mail list logo