Geoff Pack wrote:
I find that it often helps to add a border in the html
which then limits you to only using HTML 4 or XHTML 1.0 Transitional
--
Patrick H. Lauke
_
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- +
On 5/11/05 12:02 AM Patrick H. Lauke [EMAIL PROTECTED] sent this
out:
I find that it often helps to add a border in the html
which then limits you to only using HTML 4 or XHTML 1.0 Transitional
Would that be bad? If so, why would that be bad?
I sure read differing opinions on all this XHTML
On 11 May 2005, at 4:02 pm, Patrick H. Lauke wrote:
Geoff Pack wrote:
I find that it often helps to add a border in the html
which then limits you to only using HTML 4 or XHTML 1.0 Transitional
That is not correct.
http://dev.l-c-n.com/_temp/table_1.php
Is perfectly valid application/xhtml+xml --
Rick Faaberg wrote:
Would that be bad? If so, why would that be bad?
Not necessarily bad, no.Just thought it would be worth spelling out the
implications of using border and such attributes.
Of course, the only true value of XHTML (strict) comes when you're
mixing different XML technologies in
Simon,
Am Dienstag, 10. Mai 2005 um 18:32:05 haben Sie geschrieben:
object classid=clsid:D27CDB6E-AE6D-11cf-96B8-44455354
codebase=http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=7,0,19,0;
width=400 height=300
param name=movie
Philippe Wittenbergh
That is not correct.
http://dev.l-c-n.com/_temp/table_1.php
Is perfectly valid application/xhtml+xml -- xhtml1.1
table border=0 cellpadding=1 cellspacing=0
Hmmm...interesting. Thanks for the correction. Bizarre, though, that
those attributes have been left in the
Hi All
I've got an issue that I haven't seen before. I've got a fairly simple
vertical nav with nested lists.
For some reason, the links are not displaying as block level elements in IE.
Here's the CSS
#mainnav {background:#29475d; width:182px; list-style-
type:none;padding:10px 0 10px 7px;}
Drake, Ted C. wrote:
The rest of the styles use body classes to show or hide specific
nested menus.
Does anyone see a reason why the links would not display as block? It
is causing some flashing as you mouse over the links and hit dead
air. The hover goes off and on
Hi Ted,
To fix IE,
G'day
Drake, Ted C. wrote:
For some reason, the links are not displaying as block level elements in IE.
Here's the CSS
...
#mainnav li a {display:block; border-top:1px solid #fff; padding-right:5px;
padding-left:5px; text-decoration:none;
font-weight:bold!important; color:#fff;
#mainnav li {list-style-type:none; margin:0; padding:0;display:inline;}
You can't have a block-level element within an inline one... try changing display:inline to float:left instead
cheers
kemie
...:| kemie |:...
.:| www.monolinea.com
|:.
Ding, ding, ding,
We have a winner.
I used the display:inline/display:block
combination from this Andy Budd post:
http://www.andybudd.com/archives/2003/12/css_crib_sheet_1_gaps_between_vertical_nav_elements_in_ie5/index.php
When I switched it to float:left, the nav
elements shrank
Drake, Ted C. wrote:
I could probably generalize the holly hacks to the whole site, but
for now I am doing it on the individual nav. Are there reasons why I
shouldn't just say * html li and * html a ?
Did you try to use Conditional Comments instead of CSS filetrs?
IMO, that's where this
Hi everyone,
I realize that /* */ are used to add comments to CSS, but I'm not
clear on what /* \*/ means, or what the single asterisk is used for.
Kerri
PS - I've only just joined the list so I do apologize if this is
perceived as off topic.
---
Excerpt from Ted Drake:
Kerri McKenna wrote:
Hi everyone,
I realize that /* */ are used to add comments to CSS, but I'm not
clear on what /* \*/ means, or what the single asterisk is used for.
/* */ pairs alone are comments, yes, but they are also used as hacks
when they are used in the right sequence. Some browsers
Kerri McKenna wrote:
Hi everyone,
I realize that /* */ are used to add comments to CSS, but I'm not
clear on what /* \*/ means, or what the single asterisk is used for.
Kerri
PS - I've only just joined the list so I do apologize if this is
perceived as off topic.
---
Excerpt
Hi, it's a CSS filter to rule out IE5Mac, see
http://www.dithered.com/css_filters/css_only/escaped_comment_end.html
--
Jan Brasna aka JohnyB :: www.alphanumeric.cz | www.janbrasna.com
**
The discussion list for http://webstandardsgroup.org/
Drake, Ted C. wrote:
This is a hack to send a style to Internet Explorer on windows and
not mac.
IMHO, IE CCs are a better alternative to this hack:
http://msdn.microsoft.com/workshop/author/dhtml/overview/ccomment_ovw.asp
Thierry | http://www.TJKDesign.com
On 12 May 2005, at 5:15 am, Drake, Ted C. wrote:
This is a hack to send a style to Internet Explorer on windows and not
mac.
/* \*/ hides it from IE Mac, which doesn't understand the escape \
It would be better formulated as:
'A filter to hide the next rule block from IE Mac'.
In full:
/* hide
Hi
I havent asked this for a while so it would be interesting to know what
the current trend in Browser/Operating system support is for the
freelancers/corporates on this list to see if there has been any change
in the last 6-12 months
Theoretical example 1: we used to design for 5.x browsers
I found a solution for my problem from this page:
http://www.alistapart.com/articles/alternate/
I use this function:
function setActiveStyleSheet(title) {
var i, a, main;
for(i=0; (a = document.getElementsByTagName(link)[i]); i++) {
if(a.getAttribute(rel).indexOf(style) != -1
20 matches
Mail list logo
