Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#19112 - [chromium] Developer tools bug in 5.0.342.9-1

Attached to Project: Arch Linux
Opened by Luca Gambetta (ziabice) - Thursday, 15 April 2010, 10:44 GMT
Last edited by Dan Griffiths (Ghost1227) - Sunday, 30 May 2010, 07:41 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Dan Griffiths (Ghost1227)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I'm on Arch Linux x86_64, while using Developer Tools I noticed that if you click on the "gear" icon in the "Elements" tab, the menu doesn't open.

If I do the same thing using Epiphany browser (also based on WebKit), everything works correctly.

I friend of mine told me that version 5.0.376.0 (44292) on Ubuntu works flawlessy.

Additional info:
* package version(s)

chromium 5.0.342.9-1


Steps to reproduce:
open a page, press CTRL-SHIFT-I, this opens developer tools windows, then select an element into the page, look up-right in the page for a gear in the "Styles" tab.
This task depends upon

Closed by  Dan Griffiths (Ghost1227)
Sunday, 30 May 2010, 07:41 GMT
Reason for closing:  Fixed
Additional comments about closing:  In [testing]
Comment by Dan Griffiths (Ghost1227) - Thursday, 15 April 2010, 23:26 GMT
Hopefully will be fixed in next rebuild
Comment by Luca Gambetta (ziabice) - Friday, 16 April 2010, 07:08 GMT
The problem is that I should write an article about Chromium Developer Tools showing how good they are for a magazine... :|
Comment by Luca Gambetta (ziabice) - Friday, 16 April 2010, 08:02 GMT
I can confirm that this bug is also present in official Google deb files (5.0.342.9) for Ubuntu/Debian
Comment by Federico Chiacchiaretta (baghera) - Tuesday, 11 May 2010, 14:31 GMT
Well new beta version 5.0.375.38 has been released, maybe also in that revision this bug is fixed.
Waiting for an update then :)
Comment by Dan Griffiths (Ghost1227) - Sunday, 30 May 2010, 00:58 GMT
I'm getting ready to release a new package that fixes this issue, and drastically updates the package in general. Thanks for your patience! Hopefully, now that chromium has a slightly saner and more reliable beta branch, issues will be resolved quicker.

Loading...