Launchpad itself

Launchpad doesn't display in the omniweb browser

Bug #132154 reported by Steve Alexander
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Katie Moody

Bug Description

Launchpad does not display when used from the OmniWeb browser.

OmniWeb is a browser for Mac OS X, sold by http://www.omnigroup.com/applications/omniweb/

Revision history for this message
Steve Alexander (stevea) wrote :

Please attach a screenshot of what https://bugs.launchpad.net/launchpad/+bug/132154 (this page) looks like in omniweb.

Changed in launchpad:
assignee: nobody → mpt
status: New → Incomplete
Revision history for this message
Jens Vagelpohl (dataflake-deactivatedaccount-deactivatedaccount) wrote :

With Omniweb, most of the "site furniture" elements are not displayed, and the main "content well" is completely empty - see the attached screen grab.

Just FYI, OmniWeb builds on Apple's WebKit, just like Safari, and is usually about one generation behind the latest Safari WebKit.

Steve Alexander (stevea)
Changed in launchpad:
importance: Undecided → Medium
status: Incomplete → Confirmed
Revision history for this message
James Henstridge (jamesh) wrote :

PNG version of above attachment, as it is easier to view from within a web browser.

Jens: do you have any idea of what version of webkit OmniWeb is using? Maybe it has it in the about dialog?

Revision history for this message
Jens Vagelpohl (dataflake-deactivatedaccount-deactivatedaccount) wrote :

There's no information in the About dialog, but apparently there's some in the User-Agent header:

http://www.omnigroup.com/applications/omniweb/developer/

Looking at their release notes they claim to have done small customizations to WebKit, and they cherry-pick bug fixes from the Apple repository when needed.

Here's the Usr-Agent string from the latest OmniWeb (5.5.4):

"Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US) AppleWebKit/420+ (KHTML, like Gecko, Safari/420) OmniWeb/v607.17"

Here's the same from Safari (2.0.4)

"Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en) AppleWebKit/419.3 (KHTML, like Gecko) Safari/419.3"

These numbers seem to indicate that OmniWeb may even be *ahead* of Safari, it's a bit confusing.

Matthew Paul Thomas (mpt)
Changed in launchpad:
assignee: mpt → victor-choosebrilliant
Matthew Paul Thomas (mpt)
Changed in launchpad:
importance: Medium → High
Revision history for this message
Damian Gaweda (damian-choosebrilliant) wrote :

I've spend some time trying to solve the problem and I came to the conclusion that this may be a browser bug.

Here are the tests I performed on div#applications (http://launchpad.net),
which is not visible in OmniWeb. Tested with OmniWeb-5.5.4-v607.17 on MacOS X 10.4.10.

I removed all additional css in html <head>, leaving only the main style.css file.

1. div#applications { position: relative; }
   - no effect, div positioned but invisible

2. div#applications { position: absolute; top: 10px; left: 10px; }
   - no effect, div positioned but invisible

3. div#applications { position: fixed; top: 10px; left: 10px; }
   - no effect, div positioned but invisible

4. div#applications { position: fixed; top: 10px; left: 10px; }
   - div IS VISIBLE!

5. div#applications { visibility: visible; }
   - no effect

6. div#applications { display: inline; }
   - no effect

7. div#applications { display: block; }
   - no effect

8. div#applications { z-index: 9999; }
   - no effect

8. div#applications { opacity: 1; }
   - no effect

9. Using FireBug, I checked css properties inherited by div#applications from its parent elements.
   - nothing suspicious

9. Disabled JavaScript support in the browser
   - div appears after a few clicks on 'refresh'. Refresh again and it's gone. Seems random. Couldn't
     form a pattern to it.

It looks like an OmniWeb bug to me.
Obviously setting all invisible elements to position: static (which seems to work in this example) is not a solution.
I'm going to look further into this problem tomorrow using the
Divide-and-Conquer method (thanks for suggestion, Steve).

Revision history for this message
Damian Gaweda (damian-choosebrilliant) wrote :

This problem is related to an Omniweb's bug originating from an old Safari/Webkit bug.

Quote from http://www.quirksmode.org/bugreports/archives/safari/index.html
"In Safari the entire body disappears if you set position: relative on the HTML first, and then on the BODY. (...)
Workarounds include using quirks mode, or playing it safe and avoiding setting positioning to the html element."

Despite the fact that the latest Omniweb announces itself as AppleWebKit/420+ (newer than the latest Safari),
this bug had not been fixed.

I set "html { position: static }" in css, which seems to solve the problem without affecting rendering in other browsers.

Revision history for this message
Jens Vagelpohl (dataflake-deactivatedaccount-deactivatedaccount) wrote :

Is there a timetable for this change to make it into the launchpad instances on bugs.launchpad.net?

Revision history for this message
Steve Alexander (stevea) wrote :

We'll try it out on bugs.edge.launchpad.net first. That's the service we use to test cutting-edge code against the production database.

If you join the team https://edge.launchpad.net/~launchpad-beta-testers, you'll be automatically redirected to use the edge servers instead of the regular launchpad servers. You can switch back using a control that appears on https://launchpad.net/.

I expect the fix to appears on bugs.edge.launchpad.net within the next 36 hours.

Revision history for this message
Christian Reis (kiko) wrote :

Landed in RF 5098.

Changed in launchpad:
status: Confirmed → Fix Committed
Revision history for this message
Jens Vagelpohl (dataflake-deactivatedaccount-deactivatedaccount) wrote :

FYI: OmniWeb 5.6 was just released, which appears to fix the issue all by itself, since I am actually able to view and comment on this bug report using OW. They updated the version of WebKit:

OmniWeb 5.6's user-agent string is:
Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US) AppleWebKit/522+ (KHTML, like Gecko, Safari/522) OmniWeb/v613

OmniWeb 5.5's user-agent string is:
Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US) AppleWebKit/420+ (KHTML, like Gecko, Safari/420) OmniWeb/v607

IMHO if you believe your fix is questionable or you are not 100% sure if it affects other browsers negatively it would be fine to pull it completely.

Revision history for this message
Steve Alexander (stevea) wrote :

Jens, thanks for the feedback, and the note about a new version of OmniWeb. The workaround for Launchpad is running on edge: https://bugs.edge.launchpad.net/launchpad/+bug/132154

We're sure it doesn't affect other browsers, so we'll keep it in, anyway.

Christian Reis (kiko)
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.