Some pages don't work properly with Opera in Bug Reports

ID:107353
 
Jan 20 2011, 5:30 pm
BYOND Version:N/A (Website Bug)
Operating System:Windows Vista Business 64-bit
Web Browser:Opera 11
Applies to:Website
Status: Deferred
This issue may be low priority or very difficult to fix, and has been put on the back burner for the time being.
Descriptive Problem Summary:

Problem is simple. Some of the websites pages cannot be scrolled down while using Opera to browse them.
Most common pages are blogs that use the default layout (I think it's the default layout)

These pictures explain it all.

http://files.byondhome.com/TheMagicMan/firefox.jpg
Using firefox you can clearly see the page can be scrolled down.

http://files.byondhome.com/TheMagicMan/opera.jpg
Using Opera the page just cuts off. No scroll bar, Page up/down do not work on the keyboard, nothing can be done to scroll down the page, even though there is clearly more stuff down the page.

#1 Jan 21 2011, 8:44 am
While our main CSS had height:100% and min-height:100% attributes in the body selector that I'm pretty sure are no longer needed, the new blog template does not have this.

As far as I can tell this is strictly an Opera bug. I mean obviously the fact that it's having this scroll issue at all is a bug on their end because it's not CSS compliant, but I'm not sure there's a workaround at all. There's nothing in our page layout that should cause problems. The box columns are absolutely positioned, but that's not even new to this layout--nor should it break scrolling. It seems Opera is not correctly registering the height of the page, and that's something we just can't fix. I strongly suggest sending them a bug report.
#2 Jan 25 2011, 2:07 pm
Deferring this issue pending poster's response from Opera development team regarding their bug. If they suggest a workaround that can be implemented without breaking other browsers, it will be done. If there is no workaround, this report should be closed.
#3 Mar 17 2011, 7:32 pm
I can't help but notice that most of the blogs with custom CSS do not have this problem. I know that it's an Opera bug but there is obviously some sort of workaround and it is very, very, very annoying to have to switch browsers just to read blogs.
#4 Mar 17 2011, 10:43 pm
If you can provide examples of which blogs have the issue and which don't, that might help us narrow down where Opera is choking and might suggest a workaround, though I have my doubts there's an easy fix at our end.

But I also insist this same information should be reported to Opera's developers as well; I don't know if TMM ever did, but if so you can add that info to his bug report.
#5 Mar 24 2011, 10:56 am
I'm not sure what the problem is as I don't have the time, skills, or effort to track it down, but this works properly and this does not.
#6 Mar 24 2011, 11:49 am
Hiro the Dragon King wrote:
I'm not sure what the problem is as I don't have the time, skills, or effort to track it down, but this works properly and this does not.

The one that works has a hash that's forcing the scrollbar down, which is probably forcing Opera to reevaluate the page in a way that it does not do otherwise.
#7 Mar 24 2011, 12:29 pm
Is there anyway to force it do that on a regular basis, assuming the user is using Opera?

Also...
Work:
SilkWizard
Oasiscircle
Bootyboy
LummoxJR
Tom

Do Not Work:
BYONDVolunteers
Well, the default layout. I have run into a handful of non-default layouts that do not scroll either, but I'll be damned if I can actually find them now.
#8 Mar 24 2011, 12:41 pm
Hiro the Dragon King wrote:
Is there anyway to force it do that on a regular basis, assuming the user is using Opera?

To recalculate? The only method that I'm aware of so far that does this is jumping to a hash tag on the page. That's obviously not a solution that can be used on other pages. If there's another way to force recalculation I'm not aware of it. Also, such an option would probably have to be done via JavaScript.

The dividing line seems to be the blogs that use the new default CSS as their starting point as opposed to the old. But I have absolutely no idea what aspect in particular of the CSS is triggering the bug.

Has this even been reported to Opera's developers yet? This is their bug to fix, not ours, and while I'm happy to use a simple CSS workaround if one is available, no other browser experiences this problem.