Summary: | Sorting columns on finance.google.com doesn't work | ||
---|---|---|---|
Product: | WebKit | Reporter: | Steven Canfield <scanfield> |
Component: | Evangelism | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | CC: | ddkilzer, salvo.privitera, vicki |
Priority: | P2 | Keywords: | GoogleBug, InRadar |
Version: | 523.x (Safari 3) | ||
Hardware: | Mac | ||
OS: | OS X 10.4 | ||
URL: | http://finance.google.com/finance/portfolio?action=view&pid=1 |
Description
Steven Canfield
2007-05-09 02:35:37 PDT
Confirmed. This page works when spoofing as FIrefox 2.0.0.2. See Bug 16840. *** Bug 16840 has been marked as a duplicate of this bug. *** Is there anything I can do on the "evangelism" front? I'd like to help get this bug knocked away. (In reply to comment #3) > Is there anything I can do on the "evangelism" front? I'd like to help get this > bug knocked away. The fastest way to get this fixed is to notify the employee at Google responsible for finance.google.com, or if they have an internal Safari evangelist, to notify that person. Second best would be to ask someone you know that works at Google to find said employees and forward a message or open a bug on their internal bug tracking tool. Third option would be to use Google public forums (on groups.google.com?) to post information about the issue and linking back to this bug. Such a post may get noticed by the correct people there, and eventually get fixed. Above all, when you do contact someone, be as courteous, polite and helpful as possible. Yesterday I opened a bug report on http://www.google.com/support/finance/bin/request.py. Salvatore (In reply to comment #4) > (In reply to comment #3) > > Is there anything I can do on the "evangelism" front? I'd like to help get this > > bug knocked away. > > The fastest way to get this fixed is to notify the employee at Google > responsible for finance.google.com, or if they have an internal Safari > evangelist, to notify that person. > > Second best would be to ask someone you know that works at Google to find said > employees and forward a message or open a bug on their internal bug tracking > tool. > > Third option would be to use Google public forums (on groups.google.com?) to > post information about the issue and linking back to this bug. Such a post may > get noticed by the correct people there, and eventually get fixed. > > Above all, when you do contact someone, be as courteous, polite and helpful as > possible. > This appears to work now. Please reopen the bug if you still see the same issue. |