Conversation
Because holy @#$@# is that annoying. :-P
|
@mat-mo Does the previous/next article navigation in the bottom right look as expected? (I imagine it doesn't. ;-) ) |
| border-radius: 3px 0 0 3px; | ||
| } | ||
|
|
||
| html:not(.rtl) .stick .btn + .btn, |
There was a problem hiding this comment.
Can't we avoid the :not(.rtl) thanks to the .rtl below, overriding the properties?
There was a problem hiding this comment.
Not quite elegantly. Options include border-left-width: 0; instead of none, so you can easily restore it to some px value (probably the best alternative) and possibly also some invalid value.
There was a problem hiding this comment.
The alternative looks like this:
diff --git a/p/themes/Origine/origine.css b/p/themes/Origine/origine.css
index 86210940..5f90fb1b 100644
--- a/p/themes/Origine/origine.css
+++ b/p/themes/Origine/origine.css
@@ -150,16 +150,16 @@ html.rtl .stick input:last-child {
border-radius: 3px 0 0 3px;
}
-html:not(.rtl) .stick .btn + .btn,
-html:not(.rtl) .stick .btn + input,
-html:not(.rtl) .stick .btn + .dropdown > .btn,
-html:not(.rtl) .stick input + .btn,
-html:not(.rtl) .stick input + input,
-html:not(.rtl) .stick input + .dropdown > .btn,
-html:not(.rtl) .stick .dropdown + .btn,
-html:not(.rtl) .stick .dropdown + input,
-html:not(.rtl) .stick .dropdown + .dropdown > .btn {
- border-left: none;
+.stick .btn + .btn,
+.stick .btn + input,
+.stick .btn + .dropdown > .btn,
+.stick input + .btn,
+.stick input + input,
+.stick input + .dropdown > .btn,
+.stick .dropdown + .btn,
+.stick .dropdown + input,
+.stick .dropdown + .dropdown > .btn {
+ border-left-width: 0;
}
html.rtl .stick .btn + .btn,
@@ -171,7 +171,8 @@ html.rtl .stick input + .dropdown > .btn,
html.rtl .stick .dropdown + .btn,
html.rtl .stick .dropdown + input,
html.rtl .stick .dropdown + .dropdown > .btn {
- border-right: none;
+ border-left-width: 1px;
+ border-right-width: 0;
}
.stick input + .btn {There was a problem hiding this comment.
It looks a bit lighter, maybe? No strong preference
There was a problem hiding this comment.
I went with the current version because I figured it's slightly easier to parse (if not ltr then border-left:none, elseif ltr then border-right: none) but I'm fine with any approach. A similar option is to add html.ltr as well.
|
So we lack adding |
|
Indeed. For testing I used this simple change, that should also be put in install.php. diff --git a/app/layout/layout.phtml b/app/layout/layout.phtml
index 498cc447..d08261d7 100644
--- a/app/layout/layout.phtml
+++ b/app/layout/layout.phtml
@@ -1,6 +1,6 @@
<?php FreshRSS::preLayout(); ?>
<!DOCTYPE html>
-<html lang="<?= FreshRSS_Context::$user_conf->language ?>" xml:lang="<?= FreshRSS_Context::$user_conf->language ?>">
+<html lang="<?= FreshRSS_Context::$user_conf->language ?>" xml:lang="<?= FreshRSS_Context::$user_conf->language ?>" dir="rtl" class="rtl">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="initial-scale=1.0" />I was thinking it could perhaps be put in the |
|
I suggest we add a line 'dir' => 'rtl',in https://github.com/FreshRSS/FreshRSS/blob/dev/app/i18n/en/gen.php |
Co-Authored-By: Alexandre Alapetite <[email protected]>
|
Yes @Frenzie , looks good 👍 |
|
I did this manually, but I just noticed https://github.com/cssjanus/cssjanus https://github.com/cssjanus/php-cssjanus Which opens up an easy path to a completely different approach. |
|
I'm thinking this CSSJanus approach may be better than this PR, mainly because it should require (almost) no effort to maintain, not to mention manually going through all the themes would add up even if it can be slowly spaced out. Using the PHP port it could potentially even be integrated into the program itself. The basic idea is a bit different though. Instead of localized overrides in the same CSS file, you'd generate a When minor touchups are required, the "current" approach ( There are actually also newer CSS attributes that may mostly avoid the issue, but they're not supported by Edge yet. https://drafts.csswg.org/css-writing-modes-4/#flow-relative |
|
Can we close this PR in favor of #2678? |
|
I believe the other approach is much better in principle, yes. |




Fixes #673.
Now obviously this only fixes one thing when there are at least a dozen similar issues, but this principle is my proposed solution to all of them.
Edit: to clarify, basically anything that says something like
position: absoluteorfixedis likely affected. So areborder-left/right. The good news is that anything that isn't absolutely positioned should largely Just Work™.This change is