310135 - Google map balloon displays one word per line

Status: NEW

(Core :: Layout: Positioned, defect)

Description

[Paul]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 (ax)
Build Identifier: Firefox/1.5beta (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 (ax)

In Google Maps, the balloons containing html render one word per line. The
Google Maps API doc page I listed in "URL" is an example where I verified my own
problem (at the bruesch.net URL)

Reproducible: Always

Steps to Reproduce:
1.In the google.com/apis URL, simply click on one of the red "Markers" and note
the difference between 1.5 beta and 1.0.6
2.In the bruesch.net URL, click a couple points on the map, which adds red
"Markers" at each spot you click.
3.Click on one of those red markers and note the layout difference between 1.5
beta and 1.0.6 (and -- dare I say -- IE!)
THANKS!

Actual Results:  
In the google maps API URL:
 Marker
  #10

At the bruesch.net URL:
 Point #1
 Lon:
 -92.932874
 Lat:
 45.025783
 Unit Dist:
 0.39832724
 Total Dist:
 2.938439365
 Close Route To Start
 Connect To Here And
 Reverse To
 Start
etc. etc. etc.

Expected Results:  
In the google maps API URL:
 Marker #10

At the bruesch.net URL:
 Point #1
 Lon: -92.932874
 Lat: 45.025783
 Unit Dist: 0.39832724
 Total Dist: 2.938439365
 Close Route To Start
 Connect To Here And Reverse To Start
etc. etc. etc.

Comment 1

[zug_treno]

Reproducible with Mozilla 1.8a6 but WFM with Mozilla 1.8a5.

Comment 2

[W. Pichler]

This bug is reproducable on Linux and windows only with FF 1.5. Should be fixed.

Comment 3

[Paul]

FYI... per a suggestion on the Google maps developer discussions, I wrapped the html with  a <div> tag with a width, and it now displays correctly... e.g.

var html = "<div style='width:244px; font-size:x-small;'>\
  Point #"+index+"<br />\
  Lon: "+formatDecimal(point.x)+"<br />\
  .
  .
  .
  </div>"

Comment 4

[W. Pichler]

Yes, you can also use style=white-space: nowrap

But this is also only a workaround for a rendering bug of the gecko engine of FF 1.5.

So far hundreds of Google maps infowindows will be broken with the new firefox.

Comment 5

[Danny D'Amours]

I can confirm that I am seeing this bug as well.

Go to: http://danny.damours.net/maps/jserror.html and click on the marker.

FF 1.5 (Windows) has the text at 1 words per line while IE or FF 1.07 (Linux) works fine.

I also get a bunch of Javascript error in the console. 
Error: The "coords" attribute of the <area shape="poly"> tag is not in the "x1,y1,x2,y2 ..." format. 

Comment 6

[darren]

this bug is confirmed with me... I had to apply the nowhitespace HACK to accomodate the 1.5 browser. Consider fixing this issue, that for once IE has become better at you for something. Of course this works with FF 1.07. Safari and 1.5 are the ones that this breaks on

Comment 7

[zug_treno]

Also reproducible with SeaMonkey 1.0b and SeaMonkey 1.5a/20060124 so I guess this bug belongs to Product: Core, Component: Layout.

Comment 8

[Mike Orb]

This may not be an infowindow only issue. I created my own info-window style API at http://dallas.foodinspect.com/bymap/. I too have been seeing this problem under FF1.5 on Windows. 

Comment 9

[Boris Zbarsky [:bzbarsky]]

This looks like a regression from the fix for bug 201897 (the testcase has multiple abs pos divs nested inside each other, all with auto width).  The reflow branch should fix this.  Which means it'll be fixed in Firefox 3...

A minimal-ish testcase is:

data:text/html,<div style="position:absolute"><div style="position: absolute">This should be on one line

Comment 10

[Wayne Mery (:wsmwk)]

comment 9 testcase still renders multiple lines FF 3.1b3

Comment 11

[BugBot [:suhaib / :marco/ :calixte]]

The severity field for this bug is relatively low, S3. However, the bug has 11 votes.
:dholbert, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Comment 12

[BugBot (nomail) [:suhaib / :marco/ :calixte]]

The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.