Last modified: 2013-08-15 16:10:23 UTC
I confirmed by docomo (NTT). Occur on every page. The image below has been reported in Twitter. https://twitter.com/#!/pinpain/status/190974853053022208/photo/1/large https://twitter.com/#!/pinpain/status/190975115981357056/photo/1/large
Wow, that's.... old-school compatibility bugs. :P May need to add /*<!--*/ ... /*-->*/ into the <style> tag.
(In reply to comment #0) I forgot to write. The text portion of the script and style elements in the head element was being displayed.
This phone got served non-mobile site, so the problem is with squid redirector. Do we know this phone's model and user-agent?
(In reply to comment #3) > This phone got served non-mobile site, so the problem is with squid redirector. > Do we know this phone's model and user-agent? "P902i" is type of mobile phone that I used to confirm. The user-agent is starting with "DoCoMo/2.0 P902i". It has also been confirmed by other phones like the previous image. In jawp, Reported model is following. * F-09Bă=> DoCoMo/2.0 F09B * L706ie => DoCoMo/2.0 L706ie Reference * User-Agent of Docomo mobile phone (lang:ja) http://www.nttdocomo.co.jp/service/developer/make/content/spec/useragent/index.html
So, if this is an issue of the phone not being detected as a phone, do you want to add it? We ops can certainly merge a change like that but i would expect the mobile team to decide if it's worth it and provide the change.
Max: Could you ansewr comment 5?
We already redirect everything with "docomo" (case-insensitive) in user-agent to mobile site. This, however, also was the case at the time of report. I wonder if we can get hold of a few ancient crappy phones to actually test on them...
