Re: [css-d] tbody space inside table
Nevermind! I remember i have to set border-spacing and border-collapse properties. Sandy wrote: > Can someone direct me to some information on how to get tbody not to be > indented inside table? > there seems to be space surrounding it but its not margin or padding, > some default style i dont know how to get rid of. > > __ > css-discuss [cs...@lists.css-discuss.org] > http://www.css-discuss.org/mailman/listinfo/css-d > List wiki/FAQ -- http://css-discuss.incutio.com/ > List policies -- http://css-discuss.org/policies.html > Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ > > > __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] tbody space inside table
Can someone direct me to some information on how to get tbody not to be indented inside table? there seems to be space surrounding it but its not margin or padding, some default style i dont know how to get rid of. __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Can't figure out this white space above my menu in IE...
Michael Stevens wrote: > Are you saying that this: > [...] > should be coded like this (one long string of text) Not necessarily, although it would have an effect on IE's whitespace bug. A more normal procedure, for me, would be to have only the image in that td - packed tightly, and place the map elsewhere where it didn't provoke IE's bug. I have instructed Tidy to remove any indentations and other whitespace in my source-code, and it isn't only because I personally find unindented source-code easier to read. 1: it results in images and other elements getting tightly packed in their containers - whenever possible. Most whitespace problems in IE are avoided then. 2: those phony tags-across-lines some use to avoid whitespace problems on lists and such in IE are avoided - I find it easier to apply controlled 'hasLayout' triggers to fix those cases. What my Tidy does actually looks pretty much like your packed example - which is fine with me. Most coders seem to prefer a more lined-up source-code, but then one also have to keep IE's bugs and the effect of rendering modes in mind while styling. regards Georg -- http://www.gunlaug.no __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Can't figure out this white space above my menu in IE...
-Original Message- From: Gunlaug Sørtun [mailto:gunla...@c2i.net] 2: IE sees whitespace (text) wherever it can in any mode. It's an old bug. So you better close all gaps in the source-code - yours is wide open, and make sure you keep track of what's block and what's inline elements and modify 'display' when necessary. -- Are you saying that this: http://info.orderprinting.com/why_use_orderprinting.html";> http://info.orderprinting.com/why_use_orderprinting.html";> http://info.orderprinting.com/why_use_orderprinting.html";> should be coded like this (one long string of text): http://info.orderprinting.com/why_use_orderprinting.html";>http://info.orderprinting.com/why_use_orderprinting.html";>http://info.orderprinting.com/why_use_orderprinting.html";> That would really blow... Mike __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Can't figure out this white space above my menu in IE...
Michael Stevens wrote: > So, where is this mysterious TEXT element that IE is fabricating? We > have to fight this pig enough without it making stuff up... :( 1: all browsers render your page in quirks mode[1] - old pre-standard, so they can literally make up as much stuff as they want. Each browser has its own quirks mode variant, which means it can be slightly more complicated to style them in line in that mode than in standard mode. 2: IE sees whitespace (text) wherever it can in any mode. It's an old bug. So you better close all gaps in the source-code - yours is wide open, and make sure you keep track of what's block and what's inline elements and modify 'display' when necessary. regards Georg [1]http://gutfeldt.ch/matthias/articles/doctypeswitch/table.html -- http://www.gunlaug.no __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Menu-issue
2008/12/29 >> Any suggestions in this direction. > > UDM: > http://www.udm4.com/ > > PMM2: > http://www.projectseven.com/products/menusystems/pmm2/ > > * Yahoo! User Interface menu: http://developer.yahoo.com/yui/menu/ Thanks to both of you for these links. The only problem are, I don't have Dreamweaver or anything like. So it must bee something like the Yahoo-thing, maybe. -- Regards / Mhv. Ib K. jensen __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Can't figure out this white space above my menu in IE...
display: block took care of it... So, where is this mysterious TEXT element that IE is fabricating? We have to fight this pig enough without it making stuff up... :( Thanks... Now I'll see what I can figure out about the misplaced boxes in the FedEx section. Mike -Original Message- From: David Hucklesby [mailto:davidh...@writeme.com] Yes. IE is placing the image on the baseline of the "text" it "sees" in the table cell, leaving space for non-existent text descenders. In your test_bct.css add one of these declarations to the rule for the 'img' selector: vertical-align: bottom; - or - display: block; __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Can't figure out this white space above my menu in IE...
On Mon, 29 Dec 2008 08:34:35 -0700, Michael Stevens wrote: > http://bctaztest.bigmikes.org/test.html > http://bctaztest.bigmikes.org/test_bct.css > > ~5 pixels above the burgundy menu bar. ... > > Any idea on the extra white space above the menu? > Yes. IE is placing the image on the baseline of the "text" it "sees" in the table cell, leaving space for non-existent text descenders. In your test_bct.css add one of these declarations to the rule for the 'img' selector: vertical-align: bottom; - or - display: block; > I also just noticed my text boxes in the FedEx section are off... gotta look > into that > as well... > The whole page looks odd this end. Probably because I have Flash turned off in all my browsers, and you have not provided any alternative content? Cordially, David -- __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Menu-issue
From: "Ib Jensen" > 2008/12/28 Al Sparber : >> From: "Ib Jensen" >>> 2008/12/28 David : > >> You would be better off with a nice single-level CSS menu across the top >> with sidebar context menus. > > You mean, just a single-level drop-down menu. And sub-menus in the > sidebar. > As the one in : ikjensen.dk Yes. That approach is more usable. > The menu you have is extremely unusable - even >> in the browsers in which it works. For that type of menu you really >> should >> be using a scripted one. > > Any suggestions in this direction. UDM: http://www.udm4.com/ PMM2: http://www.projectseven.com/products/menusystems/pmm2/ -- Al Sparber - PVII http://www.projectseven.com The Finest Dreamweaver Menus | Galleries | Widgets http://www.projectseven.com/go/pop The Ultimate DW Menu System __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Menu-issue
On 29/12/08 09:24, Ib Jensen wrote: > The menu you have is extremely unusable - even >> in the browsers in which it works. For that type of menu you really should >> be using a scripted one. > > Any suggestions in this direction. If you want something out of the box: * Ultimate Drop Down Menu: http://www.udm4.com/ * Yahoo! User Interface menu: http://developer.yahoo.com/yui/menu/ The fundamentals of keyboard accessibility here are reasonably straightforward. If submenus are to be accessible with the keyboard, ensure you can open, select, and close menu items with the keyboard. Using standard controls (buttons and links) with "click" handlers is an easy way to achieve this. Counter-intuitively any activation of a standard control (e.g. by pressing enter with the keyboard, by speaking the control name to speech recognition software, by pressing on a iPhone touchscreen) fires a 'click' event - it doesn't need to be a mouse. Alternately, you might choose to make top-menu items hub pages. In that case, you might choose to make the top-menu items simple links, with hover listeners attached to show dropdowns. That way, when used from the keyboard, you'd activate the links to go through to the hubpage and delve further into the website from there. Either way, ensure that "hidden" items either cannot be focused with the keyboard or are made visible on focus; it's crucial that users understand where focus is and what happens if (for example) they press Enter. (You'll likely want to track focus and blur events for this.) Personally, I'd avoid dropdowns for a content-driven website. I think it's better to keep the options presented to the user simple, relevant, and visible, rather than arrayed in all their complexity hidden behind functionality that varies from site to site. -- Benjamin Hawkes-Lewis __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] Can't figure out this white space above my menu in IE...
http://bctaztest.bigmikes.org/test.html http://bctaztest.bigmikes.org/test_bct.css ~5 pixels above the burgundy menu bar. With no Firebug in IE it makes it difficult to figure things out... Using the IE Developer Toolbar I can see that the TD cell that holds the header image is containing the problem. The image is not the problem, though. In the IE DT I see #text# in the cell but I can't find any text in the cell. It's an image and three image maps. And before you lay into me, yes, this site will be redesigned shortly getting rid of most of the tables. For now I just need to get it working with a new color scheme. Any idea on the extra white space above the menu? I also just noticed my text boxes in the FedEx section are off... gotta look into that as well... Thanks, Mike __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Menu-issue
2008/12/28 Al Sparber : > From: "Ib Jensen" >> 2008/12/28 David : > You would be better off with a nice single-level CSS menu across the top > with sidebar context menus. You mean, just a single-level drop-down menu. And sub-menus in the sidebar. As the one in : ikjensen.dk The menu you have is extremely unusable - even > in the browsers in which it works. For that type of menu you really should > be using a scripted one. Any suggestions in this direction. -- Regards / Mhv. Ib K. jensen __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/