Last modified: 2014-02-26 12:53:29 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 T62233, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 60233 - Headings in json-schema-code-samples have content language direction instead of user language
Headings in json-schema-code-samples have content language direction instead ...
Status: NEW
Product: Analytics
Classification: Unclassified
EventLogging (Other open bugs)
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
: i18n
Depends on:
Blocks: rtl
  Show dependency treegraph
Reported: 2014-01-19 18:20 UTC by Amir E. Aharoni
Modified: 2014-02-26 12:53 UTC (History)
7 users (show)

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


Description Amir E. Aharoni 2014-01-19 18:20:52 UTC
In Meta the content language is English. My user language there is Hebrew. If I read pages in the Schema namespace, the mw-json-schema-code-samples panel shows the code samples correctly with ltr direction, but the headings should be rtl, because they are in Hebrew.
Comment 1 Matthew Flaschen 2014-01-22 04:52:28 UTC
This is because it's inside the content element (#mw-content-text), which is .mw-content-ltr.  I'm not sure what the best way to address this is.  Maybe it could be moved out of the content element.  Otherwise, it would need to override it.
Comment 2 Amir E. Aharoni 2014-01-22 13:29:36 UTC
Adding the mw-content-(ltr|rtl) class according to the user language to the whole pop-up is probably the right way, but explicit dir="ltr" and class="mw-content-ltr" must be set on the code blocks.
Comment 3 Andre Klapper 2014-02-26 12:53:29 UTC
[moving from MediaWiki extensions to Analytics product - see bug 61946]

Note You need to log in before you can comment on or make changes to this bug.