[wp-trac] [WordPress Trac] #24977: Workflow change: automate RTL css generation
WordPress Trac
noreply at wordpress.org
Wed Aug 7 10:28:10 UTC 2013
#24977: Workflow change: automate RTL css generation
----------------------------+------------------
Reporter: yoavf | Owner:
Type: task (blessed) | Status: new
Priority: normal | Milestone: 3.7
Component: General | Version:
Severity: normal | Resolution:
Keywords: |
----------------------------+------------------
Comment (by mark-k):
For the sake of people reading this and are not familiar with rtling I
want to point out that rtling is many times more then just replacing
margin-left:10px with margin-right:10px;
I vote against, this is a good way for developers to keep not testing
their code in rtl with the excuse of "the tools will handle it". This
might have been a valid strategy if in theory such a tool might have been
made to work 100% of the time, but we know there are things that can not,
or are hard to handle automatically.
The two biggest problems I can think of right now are background position
which is designed to be used only in ltr without easy translation for
anything a little complex to rtl, and fliping images where needed
In addition there are JS libraries that have no support for rtl directions
in the HTML when calculation position offsets.
The most basic step of good QA is code coverage - make sure each line of
your code is executed in your test. With automatic rtling the developer
will not test the rtl code, so who will test it? when will the rtl bugs be
discovered? I think it is a real problem because AFAICT none of the main
contributors run beta versions in rtl, unless there is someone dedicated
for that in wordpress.com I'm afraid that rtl bugs will be discovered only
after the new version was released.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/24977#comment:7>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list