Comment #7 on issue 5876 by verdyp: Height and width defined for svg  
element are not honored
http://code.google.com/p/chromium/issues/detail?id=5876

Please link (duplicate) to Issue 33.
(this will add this report to incoming requests to solve this usability  
issue).

note that zooming in/out SVG still is also inconsistant with refreshes  
(press F5) as
the canvas is not properly set, and the zoom factor is applied twice (so we  
get the
square factor).

In some cases, this can even freeze the renderer (when zooming in at  
maximum level,
then pressing F5). The only solution is to close Chrome completely and  
reopening it
(hoping that the page history will be restored).

So the inconsistant (and bogous) zoom factor is a severe bug that should  
also be
corrected separately from the support of scrollbars for large images.

There are then 3 bugs
- correcting the zoom factor so that it will not be applied twice in the  
canvas
- fixing the canvas size so that a zoomed image won't be clipped by using  
the same
container size
- fixing the renderer freeze (with big zoom factors)
and a request for improvement:
- adding scrollbars for large images whose container in the canvas cannot  
fit the
current window size.

Note that these zoom bugs not only affects the SVG images rendered  
isolately (within
a default HTML canvas generated internally for embedded objects), but also  
any HTML
(or XHTML) page that contain a reference to a SVG image using <object> or  
<embed>.

----

Note also that the default HTML page generated internally when displaying  
various
document types that are not HTML (SVG, audio/video files, even plain text  
files or
GIF/PNG/JPEG images), is NOT a conforming XHTML page as it really should  
(missing
required <title></title> element, missing document type declaration or XML
declaration, missing content type..., elements without closing tags,  
deprecated non-
standard Netscape/IE attributes, incorrect CSS styles...).

This default HTML page (generated internally by the browser, and visible  
when opening
the Javascript console) just uses the old broken HTML4 syntax with legacy  
<embed>
elements and using the old compatibility mode. This can break many recent  
objects.
Please convert this default page to use <object> element instead, and make  
this
default internal HTML code a conforming XHTML page, so that the object will  
not be
loaded in a container using the "HTML Quirks" mode.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to