added a keyword, NeedsReduction - This bug needs a reduced test case.
![]() added a keyword, NeedsReduction - This bug needs a reduced test case.
|
|
![]() . . probably won't show the problem - "bug case closed".
|
|
![]() |
|
![]() but it won't be until next week as my folks are in town from Trinidad.
|
|
![]() . . I think instead I'll W3C certify Cabbage Greens which is much shorter and it screws that up pretty bad. Interestingly, if the margin is moved after loading, either in or out, it is instantly corrected. Several other of the vegetable pages behave the same.
The crash you have shown (text running over pictures and text) rarely appears on my system even on the fish page. |
|
![]() Cabbage greens displays correctly in Chrome but Safari screws up the "<br clear="left"> quite badly. Again if the margins are changed even slightly it displays correctly, but if the page is reloaded at the new margins it's bad again. I'd appreciate hearing how it looks on a Mac.
http://www.clovegard...red/cb_green.html |
|
![]() Same deal; move width slightly -- things line up, stay fixed: after moving back to original setting (as close as you can mouse.)
{sigh} Safari meets my minimal demands: adequacy. Not sure if it's still faster than FF. (NoScript is like a Swiss Army knife with 1800 blades.. maybe you could protect againse all Evil, but you must tell it about each one !!! ONE !!! incremental-Evil.) |
|
![]() and I get cascading on every Subsection.
Move the right side or left side one pixel larger or one pixel smaller, everything re-renders perfectly and lines up just like you want. Weird. |