This is a good way to go but the problem is that Chrome (Google in that case) didn’t implement the “start”/“end” CSS keywords so if you are trying to apply RTL by header you’ll see many glitches because the spacing and the directions are hard-coded.
So what needs to be done is switching the page over, looking for the glitches and adding an RTL override in the CSS so it won’t appear that way when RTL is selected.
Yaron I’d suggest first you clone the git repo v5.2.0 and make sure you can run the web site report from within gramps (you can use the sample .ged for some data), if you haven’t done that already. Than it is quit straight foreword, it is pretty much ‘self explanatory’ plus you’ll have all the source at your disposal to mess with.
I thought we were talking about the entire web interface, the reports should be fairly simply as these are static pages, can you send me an example html report?
Thanks.
I managed to fix some small CSS issues for gramps-js.
Switching to logical instead of absolute values is pretty helpful, I tried doing it manually, I now need to try and do it with the code and regenerate the website (or the docker).
This is an explanation about using logical CSS values:
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.