My favorites | Sign in
Project Logo
             
New issue | Search
for
| Advanced search | Search tips
Issue 1312: Copyright div uses common id name "copyright"
7 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  ----
Closed:  Jun 17
Type-Defect
ApiType-Javascript
Internal-1870098
Fixed-2.163


Sign in to add a comment
 
Reported by andrew.leach.1, May 20, 2009
The div holding the copyright string now uses the id "copyright". This is
highly likely to conflict with containing pages.

The id should be something which is likely to be unique in containing
pages, say "GCopyright" (or maybe "gCopyright", using g for divs and G for
API objects).

In fact every div named by the API should use a Google-specific name like that.

http://groups.google.com/group/Google-Maps-API/browse_thread/thread/af8b8446a09771f7
Comment 1 by andrew.leach.1, May 21, 2009
Add to this: in a page with multiple maps, there will be more than one element with
the same id. And, of course, giving an element an id makes it very easy for it to be
styled out of existence. Perhaps it would be better to remove the id altogether.
Comment 2 by pamela.fox, May 21, 2009
Agreed. Thanks for catching this.
Status: Accepted
Labels: Internal-1870098
Comment 3 by pamela.fox, May 24, 2009
Changing status of "Accepted" issues to "Acknowledged", to clarify their 
state.

We may not be able to resolve all bugs or fulfill all feature requests, but 
we do thank you for filing them, and we will continually revisit all 
acknowledged issues and evaluate their feasibility. Thanks!


Status: Acknowledged
Comment 4 by pamela.fox, May 30, 2009
There was some confusion with the change from the "Accepted" status to the 
"Acknowledged" status, and some developers took that to mean that their bug 
was being downgraded. This was only a wording change, not a priority 
change. We are still working on fixing many bugs (particularly the 
regression bugs), so a fix for your bug may still be coming in the future.

After a discussion in the forum, we will now use "Confirmed" instead of 
"Acknowledged". This status indicates that we have verified the bug, 
reported it internally, and it is included in the list of bugs that we 
review each week (when determining what to fix next).
Status: Confirmed
Comment 5 by pamela.fox, Jun 09, 2009
(No comment was entered for this change.)
Status: FixedNotReleased
Comment 6 by pamela.fox, Jun 17, 2009
(No comment was entered for this change.)
Status: Fixed
Labels: Fixed-2.163
Sign in to add a comment

Hosted by Google Code