search

cybersthang / gmaps-utility-library-dev

Automatically exported from code.google.com/p/gmaps-utility-library-dev
0 stars 0 forks source link

Tabs in Tabbed Max Content become 'unclickable' #102

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Use any of the examples on this page:
http://gmaps-utility-library.googlecode.com/svn/trunk/tabbedmaxcontent/1.0/docs/
examples.html
2. Open a tabbed window, select a different tab, close the window.
3. Open a new tabbed window, and select a different tab. Nothing happens.

What is the expected output? What do you see instead?
I would expect to see the contents of the tab I selected, but in stead
nothing happens.

What version of the product are you using? On what operating system?
tabbedmaxcontent.js 1.0 on XP SP3

Please provide any additional information below.
I've tried this with IE6, IE8 and Firefox 3.0.8

Original issue reported on code.google.com by syl...@gmail.com on 16 Apr 2009 at 2:02

GoogleCodeExporter commented 8 years ago 
Please change the gmaps API version from v=2.x to v=2. It looks something in 
the new
version of core API broke it. See

http://gmaps-utility-library-dev.googlecode.com/svn/trunk/tabbedmaxcontent/examp
les/

I'll look more and report the problem.

Original comment by nian...@gmail.com on 17 Apr 2009 at 4:36

GoogleCodeExporter commented 8 years ago 
The code broke at 2.153, which is probably out for just a couple days. But I 
have to
dig deep to find out which core API method failed before I can create a 
meaningful
report. It appears the GEvent refuse to add event listener under certain 
circumstance.

Original comment by nian...@gmail.com on 17 Apr 2009 at 8:42

GoogleCodeExporter commented 8 years ago 
After some digging, it looks like the current 2.x (2.153) changed some behavior
regarding maxNode's timing of attaching to DOM and GEvent.addDomListener. As a 
result
event can not be attached to a reused Dom Node any more. 
I've made some changes to accommodate that in r985. 

Pamela: The existing released MaxTabbedContent lib will break when v2.153 
becomes v2
(I did not use any "undocumented/unsupported" feature, but this is probably too
subtle for an ourtsider to precisely figure out what breaks it from v2.151 to
v2.153), can you do a quick push to release for this lib before that happens?   
Thanks!

Original comment by nian...@gmail.com on 24 Apr 2009 at 1:27

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
v2 is 2.156 as of May 14, 2009 so using v=2 won't work anymore. r997 needs to be
pushed to release.

Original comment by nian...@gmail.com on 15 May 2009 at 12:58

GoogleCodeExporter commented 8 years ago

Original comment by pamela.fox on 23 Jun 2009 at 9:22

GoogleCodeExporter commented 8 years ago 
Hello,, 

Is this bug fixed in v2.x?!
Because I'm still getting the same error when I use v=2 or v=2.x.. 

Al-Aswad

Original comment by alaw...@gmail.com on 30 Aug 2009 at 8:06

GoogleCodeExporter commented 8 years ago 
Please use dev version:
http://gmaps-utility-library-dev.googlecode.com/svn/trunk/tabbedmaxcontent/
 or download dev version to your own server.

Original comment by nian...@gmail.com on 30 Aug 2009 at 9:12