Last modified: 2013-07-23 01:48:19 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T53845, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 51845 - German Wikipedia: Astana; layout fails miserably
German Wikipedia: Astana; layout fails miserably
Status: RESOLVED DUPLICATE of bug 51628
Product: VisualEditor
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: James Forrester
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2013-07-23 01:35 UTC by John Mark Vandenberg
Modified: 2013-07-23 01:48 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Screenshot of layout (188.36 KB, image/png)
2013-07-23 01:35 UTC, John Mark Vandenberg 		Details
Add an attachment (proposed patch, testcase, etc.)

Description John Mark Vandenberg 2013-07-23 01:35:37 UTC 
Created attachment 12926 [details]
Screenshot of layout

Steps to reproduce:
1. Load https://de.wikipedia.org/wiki/Astana?veaction=edit
2. Cry

Results:
The infobox template consumes the entire editing area, and the map in it consumes more than the editing area.

Testing in Firefox and Google Chrome
Comment 1 Roan Kattouw 2013-07-23 01:48:19 UTC 
This is caused by the map of Kazakhstan (which is an SVG) rendering at native size rather than 280px, and stretching the entire infobox accordingly.

This is because the infobox template generates [Bild:Kazakhstan location map.svg|280pxpx|center|Astana (Kasachstan)]] for the image, and there's a bug in Parsoid that causes it to render images at native size when the size specification contains 'px' twice.

*** This bug has been marked as a duplicate of bug 51628 ***
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links