Re: [css-d] site check please?
Chris Blake wrote: And 'stop the presses' is wrong, 'press' is plural. Uhh, not always, and certainly not when used as Jody is using it: as part of the age old saying: Stop the presses. This goes way back to the days of the printing press and refers literally to stopping the printing presses during the printing process because some new vital piece of information needs to be added to the news. -- !-- ! Bill Brown macnim...@gmail.com ! Web Developologist, WebDevelopedia.com -- __ 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] css-d Digest, Vol 78, Issue 12
I am currently out of the office and will return on Thursday the 14th of May. If you have any urgent queries please contact Steve Lee on 0113 391 2929. Regards Peter __ 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] css or javascript hacks for firefox
Gunlaug Sørtun wrote:
Alan Gresley wrote:
If this is this bug
http://css-class.com/test/css/visformatting/floats/floats-width-auto.htm
Although dealing with vertical alignment of floats, our test case isn't
revealing just one bug.
Reordering the markup is the old solution, and it'll still work -
if that's an option.
Another option is to absolute position relevant elements, thus avoid old
float-alignment bugs altogether.
To return to what appears to be the original poster's case:
http://test3.dekkers.net/login.htm
...a fix for older Geckos will make it appear like this...
Page: http://www.gunlaug.no/tos/alien/id/test_09_0502.html
CSS: http://www.gunlaug.no/tos/alien/id/test_09_0502_files/layout00.css
Yes, it is backwards (hacking both old and new Gecko versions). I've
also ignored very old Geckos completely.
However, when dealing with a case that falls apart when subjected to the
slightest amount of font resizing in any browser anyway, such a solution
doesn't really add serious problems.
Interesting. The hack you have is.
@-moz-document url-prefix() {
:rootbody #login_form label input {margin-top: -1.3em;}
:rootbody:not(:nth-child(0)):only-of-type*|*:not(|*)
#login_form label input { margin-top: 0;}
}
Does this hack separate Firefox 3.0.1 ~ 3.0.10 from Firefox 3.5b4? I can
not test. This part of the hack,
|*:not(|
causes a parsing error. Is this fixed in Firefox 3.5b4? I must admit
that your hackery (possibly combining structural pseudo class support
and parsing errors) is hackier than mine. :-)
This is similar to a more recent test case on this list which I have
hacked to target Gecko 1.9.
http://css-class.com/test/css/visformatting/float-inline-content3.htm
With this hack.
img:not([class*=]) {margin-top:-1.3em; border-right: 4px solid red;}
/* targeting Gecko 1.9 */
Does Firefox 3.5b4 now send those images above the text line? The same
test case but with your hack.
http://css-class.com/test/css/visformatting/float-inline-content4.htm
I may learn a thing or two about CSS.
The best solution is always to leave new browser versions alone - not
hack them, but if that's not an option...
regards
Georg
I would dare say to not hack something that is not present when the
source is changed. Yes with IE this may be done but this is Gecko we are
dealing with. Also this can cause confusion between these different bugs.
https://bugzilla.mozilla.org/show_bug.cgi?id=50630
https://bugzilla.mozilla.org/show_bug.cgi?id=441259
The former does not effect Safari. Both bugs have been fixed with
Firefox 3.5b4? The later is still present in Safari.
--
Alan http://css-class.com/
Armies Cannot Stop An Idea Whose Time Has Come. - Victor Hugo
__
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] css or javascript hacks for firefox
Philippe Wittenbergh wrote:
On May 18, 2009, at 3:26 PM, Alan Gresley wrote:
Interesting. The hack you have is.
@-moz-document url-prefix() {
:rootbody #login_form label input {margin-top: -1.3em;}
:rootbody:not(:nth-child(0)):only-of-type*|*:not(|*)
#login_form label input { margin-top: 0;}
}
As I posted in the same thread, that second selector is overly complicated.
http://css-discuss.markmail.org/search/?q=css%20or%20javascript%20hacks%20for%20firefox#query:css%20or%20javascript%20hacks%20for%20firefox+page:1+mid:fk3ne66qqej6n2wc+state:results
Aha, thank you Philippe. Firefox 3.5b4 supports only-of-type.
--
Alan http://css-class.com/
Armies Cannot Stop An Idea Whose Time Has Come. - Victor Hugo
__
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] css or javascript hacks for firefox
Alan Gresley wrote: This part of the hack, |*:not(| causes a parsing error. Is this fixed in Firefox 3.5b4? I must admit that your hackery (possibly combining structural pseudo class support and parsing errors) is hackier than mine. :-) I'm not surprised :-) However, keep in mind that I only test hacks to check progress and see what one can get away with in various browser versions. I do not use hacks for anything serious. Also: validity is not an issue (for me) in such test-stylesheets. http://css-class.com/test/css/visformatting/float-inline-content3.htm Does Firefox 3.5b4 now send those images above the text line? Yes. The same test case but with your hack. http://css-class.com/test/css/visformatting/float-inline-content4.htm No. https://bugzilla.mozilla.org/show_bug.cgi?id=50630 https://bugzilla.mozilla.org/show_bug.cgi?id=441259 I usually don't check what's on such bug lists unless I run into a specific bug in a real-world case, so I have no idea what the status is for those bugs in latest versions of affected browsers. --- Those who utilize bugs in relatively new browsers for anything serious, will have to check and update every time a new version is released -- not only the browser they try to target but nearly all browsers. There are 4 major engines one has to keep track of, and one has to check at least the last 2-3 generations/versions of each. There are also between 25 and 30 individual browsers that use these 4 engines, and many lag one or more generations/versions behind the major browser on each engine. Staying on top of all these while trying to target/hack individual versions, should keep any web developer busy. If one wants to use ones time for something else, one better not enter such a hacking-race in the first place. --- Testing browsers, with hacks and all, in ways/places where it doesn't hurt no matter the outcome, is of course an entirely different matter. That's what I do... http://www.gunlaug.no/contents/wd_additions_42.html ...and I focus on engine versions, not individual, named, browsers. For each major or minor modification to my browser targeting stylesheet... http://www.gunlaug.no/contents/styles/target-browser.css ...I also test in at least two dozen browsers with engines that may be affected because they share bugs and/or proprietary selectors, and a dozen or so more that simply may not be shielded well enough. The need to provide extra shielding for non-targeted browsers, is the main reason my selector-chains are so complex and often contain nonsensical and unnecessary parts. Hackers who check only in a few browsers, tend to produce what looks like cleaner hacks, but such clean hacks tend to fail more often and end up hurting the wrong browsers. Failing hacks on regular web sites do at least as much damage for developers and end-users as all browser bugs put together, so one really shouldn't hack if one can't test the outcome in nearly all 25-30 browsers that are in use today, _and_ also make sure future (not yet released) versions are somewhat shielded. The latter means thorough testing in all new beta and RC versions, so one can keep track of progress and regress and be prepared for the final releases. Of course; no one in his right mind will hack a beta or RC version for real, so the purpose for beta/RC testing here is to make sure hacks meant for older versions won't disturb new versions. Those who want to can then check bug lists and report problems/bugs found during beta/RC testing. Such reports are usually most welcome for all browsers. -- To see, and eventually test, which hacks (selector chains) that hit the various versions, look at my page and stylesheet linked to above. Haven't checked and updated my browser targeting stylesheet in any detail since March this year, but it still seems to select the right engine versions across the board - including [Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b4)], so I'm in no hurry. Got other things on my mind these days, and complete and proper testing is time consuming. 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] css or javascript hacks for firefox
On May 18, 2009, at 3:26 PM, Alan Gresley wrote:
Interesting. The hack you have is.
@-moz-document url-prefix() {
:rootbody #login_form label input {margin-top: -1.3em;}
:rootbody:not(:nth-child(0)):only-of-type*|*:not(|*)
#login_form label input { margin-top: 0;}
}
As I posted in the same thread, that second selector is overly
complicated.
http://css-discuss.markmail.org/search/?q=css%20or%20javascript%20hacks%20for%20firefox#query:css%20or%20javascript%20hacks%20for%20firefox+page:1+mid:fk3ne66qqej6n2wc+state:results
Does this hack separate Firefox 3.0.1 ~ 3.0.10 from Firefox 3.5b4?
Yes.
I can
not test. This part of the hack,
|*:not(|
causes a parsing error. Is this fixed in Firefox 3.5b4?
Not a parse error, a warning that nth-child is not supported in Gecko
1.9.0.
As mentioned earlier, the bug you're talking about is FIXED in Gecko
1.9.1+ (fx 3.5b4), as clearly marked in the bug reports you link to.
Philippe
---
Philippe Wittenbergh
http://l-c-n.com/
__
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] Displaying/Simulating handwritten fonts on notebook paper
Hi, I encountered a peculiar use case. The business desires to display a small amount of text as a handwritten font. They want the handwritten font sitting on blue lines. This would simulate the effect of writing in a notebook. My first thought was sIFR for the fonts, but I don't think it supports the lines. Is there anything that supports this? I was thinking of using CSS to create blue borders underneath the sIFR, but then the fonts would not be sitting on the line properly. (If there is a font that actually has built-in blue underlines, sIFR would work.) Any advice would be appreciated. Sincerely, Stephen __ 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] Displaying/Simulating handwritten fonts on notebook paper
Why not use a background image of a wrapper to simulate the lines? My first thought was sIFR for the fonts, but I don't think it supports the lines. Is there anything that supports this? Regards, Vladislav http://www.ovalpixels.com/ __ 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] site check please?
wow, thank you for the screen shot. I will adjust. On May 17, 2009, at 9:06 PM, David Laakso wrote: Jody Levinson wrote: Hi, all, I've created this site: http://evamoon.net and it looks all right as far as I can see in FF and current versions of IE, but when I open the pages in DreamWeaver the left sidebar appears in the lower right and the navbar position overlaps the top of the content area. I don't really care if it looks odd in DW, but the fact that it does makes me worried that it might be broken elsewhere and I just haven't seen it. Would you all mind terribly having a look and letting me know if there are problems with the CSS? The CSS validates, though there are some warnings and the HTML mostly validates except for things related to the flash slide show. Thanks so much! (and btw, Eva Moon is my stage name) Jody Jody, I do not think you can trust how anything looks in any editor's viewer-- including DW's. While someone else may bring up the issue you wrote about, I do not see it on this end in Mac FF, Mac Opera, Mac SeaMonkey, or Mac Safari. Nor in XP IE 6/7/8. As an unrelated aside, I prefer my font-size preference (default), rather than yours. And, mind that, neither Opera nor the IE browsers are capable of scaling line-height set in pixels. A raw number for line-height will suffice. Please see http://chelseacreekstudio.com/ca/cssd/eva.png (shot at 32px min-font size in Opera). Best, Samuel Langhorne Clemens, (better known by the pen name Mark Twain) -- TroutDream Graphics, Inc. Always fresh. Never canned. http://troutdream.com 425-883-8277 928-833-8277 fax __ 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] site check please?
Hi Chris Actually, as Bill points out, stop the presses is correct in this sense. It refers to when a late breaking important news story would come in to a newspaper after the edition was already on the printing press. They'd stop the printing presses to update. The image at the bottom is just a plain old transparent gif with a black mask. I'm not wild about how the mask shows over a light background, but no mask leaves jaggedy edges on the hands. It's a tradeoff. As for the menu titles, I know the common wisdom is to make them straightforward, but since this is a site for a comic musician and supposed to be fun I thought it would be all right to play. The pages are light and few, so it's hard to get too lost. If many people disagree, I might reconsider. Thanks! On May 17, 2009, at 10:34 PM, Chris Blake wrote: On 18/05/2009, at 12:06 PM, David Laakso wrote: Jody Levinson wrote: Hi, all, I've created this site: http://evamoon.net and it looks all right as far as I can see in FF and current versions of IE, but when I open the pages in DreamWeaver the left sidebar appears in the lower right and the navbar position overlaps the top of the content area. I don't really care if it looks odd in DW, but the fact that it does makes me worried that it might be broken elsewhere and I just haven't seen it. Would you all mind terribly having a look and letting me know if there are problems with the CSS? The CSS validates, though there are some warnings and the HTML mostly validates except for things related to the flash slide show. Thanks so much! (and btw, Eva Moon is my stage name) Jody Jody, I do not think you can trust how anything looks in any editor's viewer-- including DW's. While someone else may bring up the issue you wrote about, I do not see it on this end in Mac FF, Mac Opera, Mac SeaMonkey, or Mac Safari. Nor in XP IE 6/7/8. As an unrelated aside, I prefer my font-size preference (default), rather than yours. And, mind that, neither Opera nor the IE browsers are capable of scaling line-height set in pixels. A raw number for line-height will suffice. Please see http://chelseacreekstudio.com/ca/cssd/eva.png (shot at 32px min- font size in Opera). Best, Samuel Langhorne Clemens, (better known by the pen name Mark Twain) I agree, Don't worry what Dreamweaver makes of it. It looks fine on my Safari (Version 4 Public Beta (5528.17)). If I want to know the 'scoop' I should go to the 'Snoop' button in the menu? And 'stop the presses' is wrong, 'press' is plural. Nice use of transparency in the bottom fixed image. What technique did you use? CB __ 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/ -- TroutDream Graphics, Inc. Always fresh. Never canned. http://troutdream.com 425-883-8277 928-833-8277 fax __ 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] Displaying/Simulating handwritten fonts on notebook paper
Stephen Tang wrote:
I encountered a peculiar use case. The business desires to display a
small amount of text as a handwritten font. They want the handwritten
font sitting on blue lines. This would simulate the effect of writing
in a notebook.
You could do something like this:
Markup:
p class=handwrittenspan class=content
the text
/span/p
CSS:
.handwritten {
font-family: Monotype Corsiva, cursive;
text-decoration: underline;
background: white;
color: blue; }
.handwritten:first-line {
text-decoration: underline overline; }
.handwritten .content {
background: transparent;
color: black; }
Omit the second rule if you just want the text to sit on blue lines, instead
of looking like written between blue lines.
Unfortunately there's no way to control the vertical placement of the
underline (and overline).
--
Yucca, http://www.cs.tut.fi/~jkorpela/
__
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] site check please?
On May 17, 2009, at 7:30 PM, Jody Levinson wrote: Hi, all, I've created this site: http://evamoon.net and it looks all right as far as I can see in FF and current versions of IE, but when I open the pages in DreamWeaver the left sidebar appears in the lower right and the navbar position overlaps the top of the content area. I don't really care if it looks odd in DW, but the fact that it does makes me worried that it might be broken elsewhere and I just haven't seen it. Would you all mind terribly having a look and letting me know if there are problems with the CSS? The CSS validates, though there are some warnings and the HTML mostly validates except for things related to the flash slide show. Thanks so much! (and btw, Eva Moon is my stage name) Jody Thanks everyone for your feedback. There is one page on the site that is broken in FF: http://evamoon.net/sl/index.html When I validate the HTML, it tells me there's a /div missing: # Error Line 87, Column 7: end tag for div omitted, but OMITTAG NO was specified /body You may have neglected to close an element, or perhaps you meant to self-close an element, that is, ending it with / instead of . # Info Line 42: start tag was here div id=wrapper But the page uses the exact same template as the other pages, though it's the only one that's in a subdirectory. All the code looks the same and the divs match up - I went through the template line by line and matched them up. There are some validation errors due to the iframe, but the iframe is not causing the problem. The page is broken without it and I've used the same iframe on another site page with no problem. I'm missing something! Help please! Thank you, Jody -- TroutDream Graphics, Inc. Always fresh. Never canned. http://troutdream.com 425-883-8277 928-833-8277 fax __ 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] site check please?
On 19/05/2009, at 3:57 AM, Jody Levinson wrote: The image at the bottom is just a plain old transparent gif with a black mask. I'm not wild about how the mask shows over a light background, but no mask leaves jaggedy edges on the hands. It's a tradeoff. The way around this is to save the file as an alpha transparent png. This would allow antialiasing of the arms so that they look right over any coloured background. You probably know that alpha pngs aren't supported in IE6 but there are a number of techniques for forcing it to play ball. __ 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] Site check please
Hi Link: http://ikjensen.dk Tested locally in FF 3.0.10 - IE 6/78 (IETester 0.3.3) Locally known issues: IE6 dont show my link-icons IE7 - 8 behave rather ok. As FF3. At 190% Page- or Text-zoom: IE6: Ahhh The template not made for IE6! IE7: Page got a horizontal scroll-bar, and continues out of the viewport. IE8: Page continues out of the viewport, but no horizontal scroll-bar. -- Regards / Mhv. Ib K. jensen - http://ikjensen.dk __ 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] site check please?
On 2009/05/17 19:30 (GMT-0700) Jody Levinson composed: I've created this site: http://evamoon.net and it looks all right as far as I can see in FF and current versions of IE, but when I open the pages in DreamWeaver the left sidebar appears in the lower right and the navbar position overlaps the top of the content area. I don't really care if it looks odd in DW, but the fact that it does makes me worried that it might be broken elsewhere and I just haven't seen it. Would you all mind terribly having a look and letting me know if there are problems with the CSS? The CSS validates, though there are some warnings and the HTML mostly validates except for things related to the flash slide show. Thanks so much! (and btw, Eva Moon is my stage name) As I normally do, I looked at it first in my routine browsing browser, with practical font size default, minimum size enforced, user stylesheets, and no Flash. I rather like it there. It's one of those rare sites that is not over-styled via classes and ids, with the result that a generic user stylesheet can undo most designer's CSS damage. The most noticeable thing my defenses failed to do was widen enough that the last link in the nav row doesn't spill onto a new line. Also they failed to zoom the H2 text to a legible size. All the rest of the text not embedded in an image, as a consequence of my defenses, is nicely sized to my needs. I generally don't like light on dark color schemes, but this one is an exception. :-) -- A fool gives full vent to his anger, but a wise man keeps himself under control. Proverbs 29:11 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ __ 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/
