-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge Branch: Rtl language support and computed css #2135
Conversation
- Text aligned right when direction is set to rtl - Text of RTL languages is reordered while LTR languages should be untouched
Calculations based on font size should be calculated based on the current font size, not the default.
- Only set the computed property on fallback to the passed-in value if it is not blank or "inherit". - When getting a property, only set it to the default if there is no specified value - When getting a property, call the setter with the specified value if there is no computed value
- word-spacing - letter-spacing - line-height
- background - background-attachment - background-image-resolution - background-position - background-repeat - background-size
- border (color, style, width for each side) - border-radius (for each corner) - border-spacing - outline (color, style, width) This includes generic helpers utilized by the getters/setters: - _get_width - _set_border_radius_corner - _set_style_side_type
- color (and helper methods) - image-resolution - list-style (list-style-image) - page-break-after - page-break-before - transform - transform-origin - z-index
@bsweeney I tested your computed props changes and tried to get the text align right working via I did not manage to get both scenarios working without code changes First with text-align inheritance
Second without
If I try to set the text-align: right in the set_direction method Scenario 1 works but inheritance will be destroyed as this will be called later. If I instead try to return text-align right in a new |
Getter is excluded under the assumption that the user is hooking into the generic getter/setter, which will evaluate to the correct value if no value is set. Per the spec: a nameless value that acts as 'left' if 'direction' is 'ltr', 'right' if 'direction' is 'rtl'.
- add keyword check - add dependency on direction
I reviewed the status of the code and realized I had a missed a few issues:
Try with the current rev of that branch and see if it helps. |
Ok then there seems no other way around it. Yes it works like this. |
Thoughts on how to proceed then? Complete review on this PR and merge, close the other PRs? |
I'd like to close this merge request. Instead my plan is to wait until your changes can be merged into develop and merge develop into the RTL branch where I repeat the necessary small changes. |
OK, I've merged the computed property branch. |
Ok I'll finalize the merge request next week. Beside some minor review comments I found an endless recursion problem in your merge request. Edit: I wrote them weeks before but now noted I forgot to submit the review... |
ah ha ha that's why those few comments were on an older commit. Anyway, I responded, take a look and let me know if you have any more thoughts. I'll commit a few changes and a new PR once we resolve current discussions. |
It was good. Otherwise I maybe never would have noticed my fail and you wait for my approval and I wait the fixes. ;) |
I'll wait your changes before I merge develop. |
Closed as discussed. It was only a test branch. |
No description provided.