Re: [WSG] Formatting tables
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- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Formatting tables
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 and whatever stuff as being worthwhile. Rick Faaberg ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Formatting tables
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 -- xhtml1.1 table border=0 cellpadding=1 cellspacing=0 .. http://validator.w3.org/check?uri=http%3A%2F%2Fdev.l-c- n.com%2F_temp%2Ftable_1.phpcharset=%28detect+automatically%29doctype=I nliness=1verbose=1 Doesn't mean it is a 'best practice' however. Philippe ---/--- Philippe Wittenbergh now live : http://emps.l-c-n.com/ code | design | web projects : http://www.l-c-n.com/ IE5 Mac bugs and oddities : http://www.l-c-n.com/IE5tests/ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Formatting tables
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 a single document, which is still not a viable option for mainstream sites anyway...so yes, nothing wrong with HTML 4. -- Patrick H. Lauke _ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re[2]: [WSG] Flash Satay method article
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 value=movie.swf param name=quality value=high param name=bgcolor value=#FF !--[if !IE] -- object data=movie.swf width=400 height=300 type=application/x-shockwave-flash param name=quality value=high param name=bgcolor value=#FF param name=pluginurl value=http://www.macromedia.com/go/getflashplayer; ALTERNATE CONTENT HERE (should not be displayed) /object !-- ![endif]-- /object I would do it in a slightly different way: !--[if IE] 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 value=movie.swf / param name=quality value=high / param name=bgcolor value=#FF / ALTERNATE CONTENT HERE / /object ![endif]-- !--[if !IE] -- object data=movie.swf width=400 height=300 type=application/x-shockwave-flash param name=quality value=high / param name=bgcolor value=#FF / param name=pluginurl value=http://www.macromedia.com/go/getflashplayer; / ALTERNATE CONTENT HERE / /object !-- ![endif]-- Otherwise it ssem to me that you'll loose the display of alternative content in all non IE5 browsers. And even in IE I'm not shure if cascading object-tags work. Martin. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
RE: [WSG] Formatting tables
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 DTD...another example of inconsistency in the specs, I guess... Patrick Patrick H. Lauke Webmaster / University of Salford http://www.salford.ac.uk ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] IE not displaying a link as a block level element
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;}
#mainnav li {list-style-type:none; margin:0;padding:0;display:inline;}
#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; background:#0b73c1; }
#mainnav li a:hover {background-color:#fff; color:#000; border-right:2px
solid #29475d; }
#mainnav li ul li a {background-color:#7fc4f7; color:#333; padding-
left:15px;}
#mainnav li ul li ul li a {background-color:#C7E7FF; padding-left:30px;}
#mainnav li ul, #mainnav li ul li ul, #mainnav li ul li ul li ul
{display:none;}
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
Thanks
Ted
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
Re: [WSG] IE not displaying a link as a block level element
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, try:
#mainnav a {height:1%}
HTH,
Thierry | http://www.TJKDesign.com
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
Re: [WSG] IE not displaying a link as a block level element
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; background:#0b73c1; }
Try adding a width. If a fixed width nav block, fix the width,
otherwise play with 100% (but you might need a hack to hide
that from browsers other than Windows IE)
Regards
--
Bert Doorn, Better Web Design
http://www.betterwebdesign.com.au/
Fast-loading, user-friendly websites
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
Re: [WSG] IE not displaying a link as a block level element
#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
|:.
RE: [WSG] IE not displaying a link as a block level element
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 to the size of the text and did strange floating things.
So, I added the width:1% to the list items
and Voila, the links are now block level and the white space is gone.
But, it looked horrible in Firefox, so I
dropped the two rules down to my trusty Holly Hack section.
/* \*/
* html #mainnav li {
height: 1%;
float:left;
}
* html #mainnav li a {
height: 1%;
}
/* */
And it is now looking good in both
browsers.
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 ?
At least for the height:1%
Ted
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of kemie guaida
Sent: Wednesday, May 11, 2005
10:12 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] IE not displaying
a link as a block level element
#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 insteadcheerskemie
...:| kemie |:...
.:| www.monolinea.com
|:.
Re: [WSG] IE not displaying a link as a block level element
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 declaration belong... The height:1% lets you also use padding with *regular* anchors in IE. Thierry | http://www.TJKDesign.com ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] CSS Comments
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:
But, it looked horrible in Firefox, so I dropped the two rules down to
my trusty Holly Hack section.
/* \*/
* html #mainnav li {
height: 1%;
float:left;
}
* html #mainnav li a {
height: 1%;
}
/* */
And it is now looking good in both browsers.
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
Re: [WSG] CSS Comments
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 can read through it, some skip it. more info: http://www.sitepoint.com/article/browser-specific-css-hacks ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] CSS Comments
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 from Ted Drake:
But, it looked horrible in Firefox, so I dropped the two rules down to
my trusty Holly Hack section.
/* \*/
* html #mainnav li {
height: 1%;
float:left;
}
* html #mainnav li a {
height: 1%;
}
/* */
Hi :-)
The \*/ part looks somehow like a way to mess with a specific browser's
parser so that certain parts of the CSS are ignore, although I have to
admin that I don't know what browser actually falls for this.
Normally a singe asterisk is used as a wildcard in CSS. If you have for
example this rule:
#menu * {
border-left: solid 2px #000;
}
...it will add a black 2px left-border to every element within the #menu.
I hope this helps :-)
MfG, Horst
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
Re: [WSG] CSS Comments
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/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] CSS Comments
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 ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] CSS Comments
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 from IE Mac \*/
selector {property:value}
/* end hiding from IE Mac */
Philippe
---/---
Philippe Wittenbergh
now live : http://emps.l-c-n.com/
code | design | web projects : http://www.l-c-n.com/
IE5 Mac bugs and oddities : http://www.l-c-n.com/IE5tests/
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
[WSG] Minimum browsers/OS tested for?
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 but recently stopped doing so without charging clients an extra XX% Theoretical example 2: we didn't test functionality on Mozilla before, but the increasing usage of Mozilla in site statistics convinced management to allow time for Mozilla testing etc etc -- Neerav Bhatt http://www.bhatt.id.au Need a Sydney based web standards contractor? You need my services. Recent projects for Glassonion, Freshweb, Cogentis, Ceneka ... http://www.bhatt.id.au/blog/ - Ramblings Thoughts http://bookcrossing.com/referral/neerav ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Reapplying your CSS when the page length changes
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
a.getAttribute(title)) {
a.disabled = true;
if(a.getAttribute(title) == title) a.disabled = false;
}
}
}
When I display the hidden content, which causes the page length to change,
the stylesheet is reapplied/refreshed using a call to this function.
This ensures my footer, which is absolutely positioned at the bottom of the
page, is moved to the bottom of the page when the additional content
appears, instead of overlapping with it.
The ONLY problem I have with all this is that in Firefox, the whole page
flickers when I mouseover the text that causes the additional content to
appear (and which calls the function to reapply the stylesheet). Any
suggestions for stopping the Firefox flicker?
Stephen
- Original Message -
From: Stevio [EMAIL PROTECTED]
To: Web Standards Group wsg@webstandardsgroup.org
Sent: Tuesday, May 10, 2005 10:39 PM
Subject: [WSG] Reapplying your CSS when the page length changes
I have some JavaScript code that causes some content to be displayed when
the user mouseover's an element. This extra content causes the page length
to increase.
However, I have some absolutely positioned footers. When the extra content
appears, the footer overlaps with it.
The positioning styles do not seem to be getting reapplied when the extra
content is shown.
Is there a way, perhaps just a simple JavaScript function I can use, to
tell the page to reapply the CSS to make sure everything is positioned
right when the extra content is shown?
Thanks,
Stephen
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.11.8 - Release Date: 10/05/2005
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.11.8 - Release Date: 10/05/2005
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
