Page MenuHomePhabricator

Text contained in the head element is displayed in Japanese old mobile phone
Closed, DeclinedPublic

Description

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


Version: unspecified
Severity: normal
OS: other
Platform: Other

Details

Reference
bz35969

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 12:18 AM
bzimport set Reference to bz35969.
bzimport added a subscriber: Unknown Object (MLST).

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...

MaxSem claimed this task.

Pretty sure this phone can't access WP anymore at all ever since we went HTTPS-only.