HighDots Forums  

Need help finding CSS bug in Opera

Cascading Style Sheets Layout/presentation on the WWW (comp.infosystems.www.authoring.stylesheets)


Discuss Need help finding CSS bug in Opera in the Cascading Style Sheets forum.



Reply
 
Thread Tools Display Modes
  #11  
Old   
Blinky the Shark
 
Posts: n/a

Default Re: Need help finding CSS bug in Opera - 06-16-2008 , 03:14 AM






Beauregard T. Shagnasty wrote:

Quote:
Candoer wrote:

Thanks for the suggestion! Will take a look at it and see if I can
adopt it. I have a LOT to learn about CSS. Have never tried using
it before. It is hard to teach a 70 year old dog new tricks.

That's like 10 in human years, eh? :-)

C'mon, you're only three years older than me, and I have no problem
using CSS...
I had no idea you were in your sixties, Gramps.

(I'm right behind you; I turn 61 this month. In human years, I mean.)


--
Blinky
Is your ISP dropping Usenet?
Need a new feed?
http://blinkynet.net/comp/newfeed.html



Reply With Quote
  #12  
Old   
rhino
 
Posts: n/a

Default Re: Need help finding CSS bug in Opera - 06-16-2008 , 11:57 AM







"Ben C" <spamspam (AT) spam (DOT) eggs> wrote

Quote:
On 2008-06-15, rhino <No.offline.contact.please (AT) anonymous (DOT) com> wrote:

"Ben C" <spamspam (AT) spam (DOT) eggs> wrote in message
news:slrng59ufg.681.spamspam (AT) bowser (DOT) marioworld...
On 2008-06-14, rhino <No.offline.contact.please (AT) anonymous (DOT) com> wrote:

"Ben C" <spamspam (AT) spam (DOT) eggs> wrote in message
news:slrng570l8.2lb.spamspam (AT) bowser (DOT) marioworld...
On 2008-06-14, rhino <No.offline.contact.please (AT) anonymous (DOT) com> wrote:

[re: http://westown.qqqq.ca/2000a.html]
[...]
One step forward, one step back. Or thereabouts.

IE7, FF2, and Opera now all behave identically - but not quite right. And
IE6 is badly broken.

In the HTML, the only tabs which take you to a "real" newsletter are
Jan-Feb
2000, May-Jun 2000, Jan 2004, and Jun 2004. All the other tabs take you
to
"nopagea.html", which is effectively an "under-construction" page.

For IE7, FF2, and Opera, everything is fine for the year 2000 and also
for
the years where all the issues are under construction. But when you
choose
2004, you see that the issues tabs are indented to begin at the same
point
as the 2004 tab rather than left to start at the 2000 tab. Re-reading
your
fourth suggestion, that appears to be what you want

Sort of. I hadn't thought of what would happen with the other tabs. I
see what you mean, of course they all want to start at the left.

but I'd prefer to leave the issues tab so that it always begins at the
same point as the 2000 tab. How do I do that?

Make the ul the container instead.

1. Make ul#topnav position: relative.
2. Remove position: relative from everything else.
3. Also give ul#topnav 1px of top padding. This is to prevent margins
collapsing.

The sub-menus should now all start in the same place over to the left.

Things are more messed up now, not less. Have a look....

Quote:
IE6 is so badly broken with this CSS that I don't know where to begin
with
sorting it out.

Did the original version, which didn't work in Opera, work in IE6?
The original version worked perfectly in IE7, IE6 and Firefox. Only Opera
had a problem and that problem was only that the issues tabs was at the top
of the page, rather than under the years tabs where I wanted it.

Frankly, Opera is more a "nice-to-have" than an essential for me so I'm
starting to think I'll go back to the version that I originally posted about
and live with the ugliness in Opera. Chances are that little of my audience
will be affected anyway.
Quote:
Am I asking too much in trying to get this to work in all 4 of the
browsers
I want to support?

It's quite lucky that it seems to be working in IE7. I don't know the
quirks and deficiencies of IE6 so I don't know what you can do there.

The obvious compromise is to allow yourself to change the HTML a bit. If
the subnavs weren't nested inside the li's they're the submenus of it
would be easier I think.

Nesting them like that is a sort of meaningful structure in HTML, but it
makes it a lot harder to style.
That's a semantic compromise in the HTML that I'm not crazy about but I'll
consider it for a few days.

The other option, of course, is that I can use the GIF-less version of the
two-tiered tabs, found at http://westown.qqqq.ca/2000.html, which works
perfectly in all four browsers.

--
Rhino




Reply With Quote
  #13  
Old   
Ben C
 
Posts: n/a

Default Re: Need help finding CSS bug in Opera - 06-16-2008 , 04:34 PM



On 2008-06-16, rhino <No.offline.contact.please (AT) anonymous (DOT) com> wrote:
Quote:
"Ben C" <spamspam (AT) spam (DOT) eggs> wrote in message
[...]
Make the ul the container instead.

1. Make ul#topnav position: relative.
2. Remove position: relative from everything else.
3. Also give ul#topnav 1px of top padding. This is to prevent margins
collapsing.

The sub-menus should now all start in the same place over to the left.

Things are more messed up now, not less. Have a look....
It looks like you've removed position: absolute from #topnav
ul#subnav-2000, #topnav ul#subnav-2004. Put it back.

[...]
Quote:
Did the original version, which didn't work in Opera, work in IE6?

The original version worked perfectly in IE7, IE6 and Firefox. Only Opera
had a problem and that problem was only that the issues tabs was at the top
of the page, rather than under the years tabs where I wanted it.

Frankly, Opera is more a "nice-to-have" than an essential for me so I'm
starting to think I'll go back to the version that I originally posted about
and live with the ugliness in Opera. Chances are that little of my audience
will be affected anyway.
And Opera might fix it anyway, although it's not strictly a bug.


Reply With Quote
  #14  
Old   
rhino
 
Posts: n/a

Default Re: Need help finding CSS bug in Opera - 06-21-2008 , 02:39 PM




"Ben C" <spamspam (AT) spam (DOT) eggs> wrote

Quote:
On 2008-06-16, rhino <No.offline.contact.please (AT) anonymous (DOT) com> wrote:

"Ben C" <spamspam (AT) spam (DOT) eggs> wrote in message
[...]
Make the ul the container instead.

1. Make ul#topnav position: relative.
2. Remove position: relative from everything else.
3. Also give ul#topnav 1px of top padding. This is to prevent margins
collapsing.

The sub-menus should now all start in the same place over to the left.

Things are more messed up now, not less. Have a look....

It looks like you've removed position: absolute from #topnav
ul#subnav-2000, #topnav ul#subnav-2004. Put it back.

Sorry for the delay in getting back here. I re-added the position: absolute
as per your suggestion and now the prototype works perfectly in IE7, Opera,
and FF. It's still messed up in IE6.

Quote:
[...]
Did the original version, which didn't work in Opera, work in IE6?

The original version worked perfectly in IE7, IE6 and Firefox. Only Opera
had a problem and that problem was only that the issues tabs was at the
top
of the page, rather than under the years tabs where I wanted it.

Frankly, Opera is more a "nice-to-have" than an essential for me so I'm
starting to think I'll go back to the version that I originally posted
about
and live with the ugliness in Opera. Chances are that little of my
audience
will be affected anyway.

And Opera might fix it anyway, although it's not strictly a bug.
I have a decision to make:
1. Keep the original version which works fine in IE6, IE7, and FF but breaks
in Opera.
2. Keep the current version which works fine in IE7, FF, and Opera but
breaks in IE6.
3. Go back to the drawing board and try to find something that works in all
4.

I'm leaning towards the 3rd option but won't have time for that for a bit
yet.

Thanks for all your suggestions.

--
Rhino




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.