1272606 - mail: convert all in-tree style sheets logical properties from -moz-padding-start etc. to padding-inline-start etc.

Status: RESOLVED FIXED

(Thunderbird :: Theme, defect)

Description

[Richard Marti (:Paenglab)]

Bug 1111440 is landing and we should follow as we don't know how long the -moz prefixes are working.

Comment 1

[Richard Marti (:Paenglab)]

Attachment: mail-convert.patch

This patch was generated by the command from bug Bug 1111440:
  find . -name "*.css" -exec sed -i -f mozpropsub {} \;
in the root of a mozilla-central tree, with the file mozpropsub
containing the contents:
s/-moz-padding-end\>/padding-inline-end/g
s/-moz-padding-start\>/padding-inline-start/g
s/-moz-margin-end\>/margin-inline-end/g
s/-moz-margin-start\>/margin-inline-start/g
s/-moz-border-end\>/border-inline-end/g
s/-moz-border-end-color\>/border-inline-end-color/g
s/-moz-border-end-style\>/border-inline-end-style/g
s/-moz-border-end-width\>/border-inline-end-width/g
s/-moz-border-start\>/border-inline-start/g
s/-moz-border-start-color\>/border-inline-start-color/g
s/-moz-border-start-style\>/border-inline-start-style/g
s/-moz-border-start-width\>/border-inline-start-width/g

Comment 2

[aleth [:aleth]]

Comment on attachment 8752138 [details] [diff] [review]
mail-convert.patch

rs+

Good to get rid of the prefixes. Do you know why the "inline" was added?

The linked bug is leave-open, do you know why?

Comment 3

[aleth [:aleth]]

(In reply to aleth [:aleth] from comment #2)
> Good to get rid of the prefixes. Do you know why the "inline" was added?

I mean, there's also a margin-block-start. What's the difference? Does one need to differentiate in the conversion?

Comment 4

[Richard Marti (:Paenglab)]

I don't know why they used "inline".

From MDN:
The margin-block-start CSS property defines the logical block start margin of an element, which maps to a physical margin depending on the element's writing mode, directionality, and text orientation.

The margin-inline-start CSS property defines the logical inline end margin of an element, which maps to a physical margin depending on the element's writing mode, directionality, and text orientation.

I see no real difference. But margin-block-start is only supported from Gecko 41+ and no other browser.

I think they leave it open because dbaron wrote in comment 4: "Note that there are a few tests that should be fixed up as well, but I'll do that in a later patch."

Comment 5

[Richard Marti (:Paenglab)]

Attachment: Bug1272606-additional.patch

dbaron posted a new patch with an updated script in bug 1111440:

  find ??* -type f -exec sed -i -f ../mozpropsub {} \;
in the root of the repository, with the file ../mozpropsub containing:
s/-moz-padding-end\>/padding-inline-end/g
s/-moz-padding-start\>/padding-inline-start/g
s/-moz-margin-end\>/margin-inline-end/g
s/-moz-margin-start\>/margin-inline-start/g
s/-moz-border-end\>/border-inline-end/g
s/-moz-border-end-color\>/border-inline-end-color/g
s/-moz-border-end-style\>/border-inline-end-style/g
s/-moz-border-end-width\>/border-inline-end-width/g
s/-moz-border-start\>/border-inline-start/g
s/-moz-border-start-color\>/border-inline-start-color/g
s/-moz-border-start-style\>/border-inline-start-style/g
s/-moz-border-start-width\>/border-inline-start-width/g
s/\<MozPaddingEnd\>/paddingInlineEnd/g
s/\<MozPaddingStart\>/paddingInlineStart/g
s/\<MozMarginEnd\>/marginInlineEnd/g
s/\<MozMarginStart\>/marginInlineStart/g
s/\<MozBorderEnd\>/borderInlineEnd/g
s/\<MozBorderEndColor\>/borderInlineEndColor/g
s/\<MozBorderEndStyle\>/borderInlineEndStyle/g
s/\<MozBorderEndWidth\>/borderInlineEndWidth/g
s/\<MozBorderStart\>/borderInlineStart/g
s/\<MozBorderStartColor\>/borderInlineStartColor/g
s/\<MozBorderStartStyle\>/borderInlineStartStyle/g
s/\<MozBorderStartWidth\>/borderInlineStartWidth/g

This updated the files in not themes directories.

Comment 6

[Richard Marti (:Paenglab)]

http://hg.mozilla.org/comm-central/rev/f340020a8caf
http://hg.mozilla.org/comm-central/rev/02e154545225