Re: [css-d] Cross-browser Display Issue / Problem With NOSCRIPT Validation
J Hodge wrote: Thank you, David. I am aware that scaling is problematic, and was thinking the best approach would be to write the CSS so that the content areas become scrollable once the text size is increased. RE: http://www.lostinxlation.net/sandbox3/portfolio/cybernomics1.html We are into areas of personal opinion. My opinion is the content area height should not be constrained, and that on scaling it should drive what is beneatn it from here to Havana. However, upon further consideration, it occurs to me that that it might also be beneficial to scale up the dimensions of the overall layout as well... That is one way of going about it. My /opinion/ is you may want the site to work in any screen window. One way to accomplish this is to set min/max width and provide your favorite workaround for IE6. the particular layout I'm using was one I picked for some practice in source ordering and the use of relative positioning, and it has certainly posed its own little challenges. =0) Nevertheless it is a valid concept. One can, and should (yet another opinion), set to maintain the css disabled/text browser source order: doing so can sometimes pose tricky and difficult css manipulation. And this is where others on the list are better qualified than I am to help bring this particular valid concept to a successful conclusion. (treswife at gmail dot com) Best, ~dL -- http://chelseacreekstudio.com/ __ css-discuss [EMAIL PROTECTED] 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] Cross-browser Display Issue / Problem With NOSCRIPT Validation
Good evening to everyone. Testbed: http://www.lostinxlation.net/sandbox3/portfolio/cybernomics1.html Testbed CSS: http://www.lostinxlation.net/sandbox3/css/primary.css I'm trying to get this site ready for the final cosmetic touches, and so far it is displaying correctly in the majority of modern browsers WITH JavaScript enabled. Unfortunately, when JavaScript is disabled, almost all browsers render ul#portNav incorrectly. I've had varied results from toggling the positioning between relative and absolute (with the necessary changes to top, left, etc), but nothing that has yielded cross-browser consistency. The goal is to have the ul#portNav display as it does in browsers using JavaScript, even when JavaScript is disabled. Any ideas? Secondly, Opera 9.x has some funky issues in rendering the ul#portNav as well, beyond the above issue. I found that out of FF/NN/IE/Saf/Op, it was the only one that used the primary.css (prior to adding hacks) and rendered that ul as being positioned at the *top* of the container. After adding an Opera hack to the primary stylesheet, I found that it rendered even more oddly once the scripts were turned off, so I added a noscript filter to correct the issue for Opera in the head of the affected pages. Unfortunately, a noscript in the head does not validate for either strict or transitional. Does anybody have any idea how to approach this in a way that will validate? Lastly, before I go in and start adjusting all the fonts to relative sizing, I'd love input from anybody with an eye for typesetting on how to make the right sidebar and the left sidebar look more harmonious. I've been looking at this for so long trying to get everything else sorted out that my eyes already feel like they are about to bleed Thank you in advance for your time and attention. I hope everyone is having a lovely evening. Time for me to go wrangle sick lilliputians... ~~J. (treswife at gmail dot com) __ css-discuss [EMAIL PROTECTED] 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] Cross-browser Display Issue / Problem With NOSCRIPT Validation
J Hodge wrote: Good evening to everyone. Testbed: http://www.lostinxlation.net/sandbox3/portfolio/cybernomics1.html Testbed CSS: http://www.lostinxlation.net/sandbox3/css/primary.css I'm trying to get this site ready for the final cosmetic touches I regret that any font-scaling whatsoever breaks your site with or without javascript enabled in any browser on any operating system. It may be best to tackle that before moving on to other issues. Regards, ~dL -- http://chelseacreekstudio.com/ __ css-discuss [EMAIL PROTECTED] 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] Cross-browser Display Issue / Problem With NOSCRIPT Validation
Thank you, David. I am aware that scaling is problematic, and was thinking the best approach would be to write the CSS so that the content areas become scrollable once the text size is increased. However, upon further consideration, it occurs to me that that it might also be beneficial to scale up the dimensions of the overall layout as well... the particular layout I'm using was one I picked for some practice in source ordering and the use of relative positioning, and it has certainly posed its own little challenges. =0) Thoughts on the relative merits of scrollable divs and larger dimensions, in this particular context? ~~J. (treswife at gmail dot com) __ css-discuss [EMAIL PROTECTED] 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/
