After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 651015 - ShellWindowTracker: Remove title tracking workarounds for OO.org and Firefox
ShellWindowTracker: Remove title tracking workarounds for OO.org and Firefox
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-05-25 00:01 UTC by Colin Walters
Modified: 2011-05-25 16:19 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
ShellWindowTracker: Remove title tracking workarounds for OO.org and Firefox (5.61 KB, patch)
2011-05-25 00:01 UTC, Colin Walters 		committed Details | Review

Description Colin Walters 2011-05-25 00:01:46 UTC 
LibreOffice does WM_CLASS correctly as of recently, and Firefox has for
some time.  Strip out the title pattern workarounds.
Comment 1 Colin Walters 2011-05-25 00:01:51 UTC 
Created attachment 188534 [details] [review]
ShellWindowTracker: Remove title tracking workarounds for OO.org and Firefox
Comment 2 Dan Winship 2011-05-25 15:45:11 UTC 
Comment on attachment 188534 [details] [review]
ShellWindowTracker: Remove title tracking workarounds for OO.org and Firefox

yay. i guess if there are more of these type of app in the future, then we're considering it their problem, not ours, so we don't want to keep the framework around?
Comment 3 Colin Walters 2011-05-25 16:11:18 UTC 
Attachment 188534 [details] pushed as 4cab0c9 - ShellWindowTracker: Remove title tracking workarounds for OO.org and Firefox
Comment 4 Colin Walters 2011-05-25 16:19:52 UTC 
(In reply to comment #2)
> (From update of attachment 188534 [details] [review])
> yay. i guess if there are more of these type of app in the future, then we're
> considering it their problem, not ours, so we don't want to keep the framework
> around?

Right.  We've done OK so far getting apps to fix their WM_CLASS, and even if we added title patterns back, their app would still be broken in 3.0, so.