all or part of this might turn out to be evangelism. several things get in the way of trying to use fennec on pge.com to get outage info. form submit doesn't submit on enter ----------------------------------- goto pge.com under "for my home" click on "Outage Map" click on "Outage Map" link on right side of the page on right side of the next page click into the search form under "search for" City [ ] enter "scotts valley" and hit enter on the soft keyboard. form submission doesn't seem to take, no reponse... and the page has no submit button so no search is possible zoom and pan doesn't seem to work on the google map --------------------------------------------------- looks like we are hardware excellating a zoom, but its impossible to zoom into a geographic area on the google map, say around santa cruz and scotts valley both of these actions seem to work ok on android browser

actual test url is http://www.pge.com/myhome/customerservice/energystatus/outagemap/

aaronmt: that's the definition of "Whiteboard: [website-compatibility]" does that in anyway indicate that the problem is on the website side or the client side? has anyone figured that out yet?

With a touch events enabled build, and Phony installed to spoof the Android UA, panning and pinch zooming the map works for me (although we sometimes instead pan the page instead and may have to tweak our algorithms there a bit... or maybe the targetting is off in Android... need to look. You can also pinch zoom the page so only the map is visible, in which case you can really screw yourself as you can't get back to the zoomed out page.... on a side note, its the first time I've seen pinch zoom work for Google maps! I see the form submit problem , but also see it on desktop firefox and the stock browser? Here's the url I'm using: http://pge.com/mybusiness/customerservice/energystatus/outagemap/

yeah, the form submit is not working for me on Build identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0a2) Gecko/20111207 Firefox/10.0a2 either. It was working for me on the builds I was running on the desktop at the time I filed this bug. Looks like a pretty serious regression somewhere along in the past few weeks.

wonder if someone can check real quick to see if this exists in firefox 9. if it does it would probably be stop ship.

(In reply to chris hofmann from comment #5) > wonder if someone can check real quick to see if this exists in firefox 9. > if it does it would probably be stop ship. Added qawanted keyword and CC'ing Tony. Is there any reason to believe that this affects more than just pge? Just want to know why we think this may be a block ship issue.

Why is this marked "regression"? That form submit on the url in comment 3 doesn't work in fx3.6, fx4, or fx8. It also doesn't work in Chrome dev or in Opera. As far as I can tell, this is just a broken site.

(In reply to Boris Zbarsky (:bz) from comment #7) > Why is this marked "regression"? That form submit on the url in comment 3 > doesn't work in fx3.6, fx4, or fx8. > I'm certain that the site was working reliably for me on desktop around Nov 30 -Dec 2 when my power was out and I was checking hourly to find out when it might come back on. An it was broken on mobile during this time. > It also doesn't work in Chrome dev or in Opera. > > As far as I can tell, this is just a broken site. Yeah, from more testing it sounds like it. Marcia also sees inconsistent results where some times it works, other times not. I looked a bit deeper and it really is a goofy page. The form/search box code looks like <table><tbody><tr> <td>City:</td><td><input type="text" size="10" onkeyup="javascript:search(this);"/></td> </tr></tbody></table> but it appears to only return results and some times zooms in for cities that have an outage. Seems like an unexpected way for a form looking thing to work, but I guess we should call this as works as designed on the website side.

there is some really ugly sniffing code for both desktop and mobile so we might want to get with the developers at PG & E if we revive the evangelism effort.. Stuff like var agent=navigator.userAgent.toLowerCase(); var is_iphone = (agent.indexOf('iphone')!=-1); var is_iPhoneApp = (is_iphone && window.location.search.substring(1).split("?")[0] == "app"); // if user agent says it's an iPhone AND the URL designates it came from the app... if (is_iPhoneApp) { document.write("<style type='text/css'>"); // hide all extra page elements document.write("div#top, div#banner, #page ul#main_navigation, div#sidebar_navigation, #page div#content ul.toolbar, #content .with-modules #sidebar_content, #main_column ul.promotions, div#footer, ul.page_options {display:none; width: 0;}"); // get rid of bar above page title document.write("div#content {background: none;}"); // width of whole area ... ... ...

Still doesn't submit on enter - but the search form now has a search button, which works fine. Invalid since page changed.