Bug 27878

Summary: [Qt] Several icon-buttons for ajax actions at launchpad.com are missing
Product: WebKit Reporter: Jonathan Thomas <echidnaman>
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WORKSFORME    
Severity: Normal CC: jmalonzo, vestbo
Priority: P2 Keywords: Qt
Version: 419.x   
Hardware: Other   
OS: Linux   
URL: https://bugs.edge.launchpad.net/ubuntu/+bug/390519

Jonathan Thomas
Reported 2009-07-31 06:00:53 PDT
Using Arora and Rekonq with Qt 4.5.2, there are several icon-buttons for actions such as marking duplicate bugs. To reproduce: -Go to https://bugs.edge.launchpad.net/ubuntu/+bug/390519 or any Launchpad bug that is marked as a duplicate of another bug. Next to the "Duplicate of bug #392593" there should be a yellow edit button similar to the one next to the bug summary. (This happens to be right above the duplicate text, too) This also occurs for a privacy toggle button that brings up an ajax dialog, but you can't see that unless you're part of the Ubuntu bug squad. Here is a slightly different, but perhaps related issue. (Just ask and I can file this separately) In the bug lists, (https://bugs.edge.launchpad.net/ubuntu/+source/plasma-widget-networkmanagement) the leftmost column should have little colored insect icons, but those are conspicuously gone, too.
Attachments
Jonathan Thomas
Comment 1 2009-07-31 06:02:08 PDT
..and that first sentence should be: "Using Arora and Rekonq with Qt 4.5.2, there are several icon-buttons for actions such as marking duplicate bugs which are missing."
Tor Arne Vestbø
Comment 2 2009-09-07 10:48:45 PDT
Confirmed in WebKit trunk (r48110), against both Qt 4.6 (77fd77d6) and Qt 4.5.3, on Mac OS 10.5
Jonathan Thomas
Comment 3 2009-10-21 18:55:34 PDT
I can also reproduce this with Google Chromium 4.0.223.6
Jonathan Thomas
Comment 4 2010-03-07 16:05:34 PST
They seem to have worked around this in newer versions of Launchpad. I suppose since a testcase was never made that it won't really be worth it to continue tracking this.
Note You need to log in before you can comment on or make changes to this bug.