[Webkit-unassigned] [Bug 85425] Use suitable viewport values when a Mobile DTD is used.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu May 3 12:04:56 PDT 2012


https://bugs.webkit.org/show_bug.cgi?id=85425





--- Comment #19 from Zalan Bujtas <zbujtas at gmail.com>  2012-05-03 12:04:56 PST ---
(In reply to comment #17)
> OK. If it's only google.com, then this should be an evangelism bug.
> 
> This is not a small deal. Entering magic modes based on unsupported DTDs is not something we should do unless there is huge and universally agreed benefit to it (in which case it should be standardized in HTML5).

While I totally agree with the statement of 'entering magic modes based on unsupported DTDs is not something we should do...', I am wondering if the fact, that it makes trunk compatible with iOS's Safari in this context (as far as the viewport width is concerned, not sure about the dpi) is a good enough reason to have it. 

iOS Safari uses different viewport canvas width depending whether the doctype instruction exists or not for the following simple test case
<!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.0//EN" "http://www.wapforum.org/DTD/xhtml-mobile10.dtd">
<html><body>Hello world. Welcome to our XHTML MP tutorial.</body></html>

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list