Menu
▾
▴
gramps-users
|
From: Arentas <55...@gm...> - 2019-12-06 07:10:05
|
Hi, My default web browser is Firefox, usually, I have no problems with text rendering in pages and even have not noticed anything, but until now. I have not done opened gramps web page since it moved to the new host, sure I don't know if it's the problem but I haven't spotted any issues before even with the same system I'm now (OpenSUSE TW KDE with latest Firefox). Not a big issue for me but just I thought is a good thing to report it and at the same time to ask if anyone else has similar behaviour? I have added a screenshot with FIrefox, Otter Browser and Opera browser showing altogether the same page with default 100% zoom view. And the second picture Firefox compared to Vivaldi Browser as I have no other browsers, but I think it's clear enough that something isn't right here. https://drive.google.com/folderview?id=1Vd3UrUDX2YY_Wn4oFRV3FpPwzgd_ypGA |
|
From: <Emy...@ya...> - 2019-12-06 08:14:49
|
Looks like you have to grant EACH PERSON permission to view that Google Drive image. Unfortunately, you did not say what the problem is nor where you're seeing it. I am ASSUMING the problem is not in Gramps or the Reports/Websites it generates. Are the wiki documentation pages hard to read? The new hosting service is actually using the Style Sheets now. You'll have drastically different display on the Mobile skin than the Desktop version. (Mobile users will see a link in footer of each page to swap between Desktop & Mobile display modes.) If you are a logged in User, you can choose different styles from the preferences too. -Brian On Fri, Dec 6, 2019 at 1:12, Arentas<55...@gm...> wrote: Hi, My default web browser is Firefox, usually, I have no problems with text rendering in pages and even have not noticed anything, but until now. I have not done opened gramps web page since it moved to the new host, sure I don't know if it's the problem but I haven't spotted any issues before even with the same system I'm now (OpenSUSE TW KDE with latest Firefox). Not a big issue for me but just I thought is a good thing to report it and at the same time to ask if anyone else has similar behaviour? I have added a screenshot with FIrefox, Otter Browser and Opera browser showing altogether the same page with default 100% zoom view. And the second picture Firefox compared to Vivaldi Browser as I have no other browsers, but I think it's clear enough that something isn't right here. https://drive.google.com/folderview?id=1Vd3UrUDX2YY_Wn4oFRV3FpPwzgd_ypGA -- Gramps-users mailing list Gra...@li... https://lists.sourceforge.net/lists/listinfo/gramps-users https://gramps-project.org |
|
From: Chris W. <chr...@gm...> - 2019-12-06 15:36:11
|
I use both Chrome and Firefox and hadn't taken a close look at the Gramps site since the migration, but now I do I can see that the rendering on Firefox is distinctly fainter than on Chrome (which the images that the OP posted seem to show and I guess was the issue being raised) and doesn't look that great. I can see that the style sheet uses "font-weight: lighter" for this text. In my previous life, I, so like many others, have had to deal with the vagaries and inconsistencies between browsers, and this seems to be one of those times. The issue appears to be the subject of this discussion: https://stackoverflow.com/questions/47700568/css-fonts-render-differently-in-firefox-and-chrome and it seems to be a case of living with it until the Firefox developers do something about it. On Fri, 6 Dec 2019 at 07:12, Arentas <55...@gm...> wrote: > Hi, > My default web browser is Firefox, usually, I have no problems with text > rendering in pages and even have not noticed anything, but until now. I > have not done opened gramps web page since it moved to the new host, sure I > don't know if it's the problem but I haven't spotted any issues before even > with the same system I'm now (OpenSUSE TW KDE with latest Firefox). Not a > big issue for me but just I thought is a good thing to report it and at the > same time to ask if anyone else has similar behaviour? > > I have added a screenshot with FIrefox, Otter Browser and Opera browser > showing altogether the same page with default 100% zoom view. > And the second picture Firefox compared to Vivaldi Browser as I have no > other browsers, but I think it's clear enough that something isn't right > here. > > https://drive.google.com/folderview?id=1Vd3UrUDX2YY_Wn4oFRV3FpPwzgd_ypGA > -- > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > https://gramps-project.org |
|
From: Arentas <55...@gm...> - 2019-12-06 15:59:42
|
Sorry guys for bad link to gDrive it needs permissions. I have moved to Dropbox now should be accessible, let me know if not. :)) https://www.dropbox.com/sh/k34jrl2lteqkeb8/AACA4TjH_Iq00UtLQi1czvMIa?dl=0 On Fri, 6 Dec 2019, 07:09 Arentas, <55...@gm...> wrote: > Hi, > My default web browser is Firefox, usually, I have no problems with text > rendering in pages and even have not noticed anything, but until now. I > have not done opened gramps web page since it moved to the new host, sure I > don't know if it's the problem but I haven't spotted any issues before even > with the same system I'm now (OpenSUSE TW KDE with latest Firefox). Not a > big issue for me but just I thought is a good thing to report it and at the > same time to ask if anyone else has similar behaviour? > > I have added a screenshot with FIrefox, Otter Browser and Opera browser > showing altogether the same page with default 100% zoom view. > And the second picture Firefox compared to Vivaldi Browser as I have no > other browsers, but I think it's clear enough that something isn't right > here. > > https://drive.google.com/folderview?id=1Vd3UrUDX2YY_Wn4oFRV3FpPwzgd_ypGA > |
|
From: <Emy...@ya...> - 2019-12-06 16:42:49
|
Or, if it is hard to read in Firefox, you could file a bug report for the website asking that the 'lighter' on the CSS (cascading stylesheet) be changed. Since you found the CSS file & section already, please note those to minimize the search for the line to be changed. -Brian On Fri, Dec 6, 2019 at 9:37, Chris Wood<chr...@gm...> wrote: |
|
From: Chris W. <chr...@gm...> - 2019-12-07 17:28:07
|
Done! On Fri, 6 Dec 2019 at 16:44, Emyoulation--- via Gramps-users < gra...@li...> wrote: > Or, if it is hard to read in Firefox, you could file a bug report for the > website asking that the 'lighter' on the CSS (cascading stylesheet) be > changed. > > Since you found the CSS file & section already, please note those to > minimize the search for the line to be changed. > > -Brian > > On Fri, Dec 6, 2019 at 9:37, Chris Wood > <chr...@gm...> wrote: > > -- > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > https://gramps-project.org |
|
From: Sam M. <man...@gm...> - 2019-12-09 02:03:37
|
Issue raised as: [Mediawiki]Gramps project [Wiki] website (gramps-project.org) text looks somewhat anaemic in Firefox https://gramps-project.org/bugs/view.php?id=11469 |
|
From: Arentas <55...@gm...> - 2019-12-21 22:54:48
|
Hi again, I've seen that issue is sorted out. But when looking at the web page again with Firefox it doesn't look like it's done. As before there was in some areas skinny fonts, now all regular font text is in the same state, where thin and greyish. I have a screenshot attached in this link to comparison to Opera browser https://susepaste.org/49882991 I see that in Grams bug tracker I was suggested to use custom stylesheet for firefox https://gramps-project.org/bugs/view.php?id=11469 But I can't understand this as a solved problem. I probably can make the custom look and stuff but this will not solve the problem for other users :))) And in reality I not really care about, I will find out how to read this text. but I thought I will report it as a bug. Cheers. On Sat, 7 Dec 2019 at 17:30, Chris Wood <chr...@gm...> wrote: > Done! > > On Fri, 6 Dec 2019 at 16:44, Emyoulation--- via Gramps-users < > gra...@li...> wrote: > >> Or, if it is hard to read in Firefox, you could file a bug report for the >> website asking that the 'lighter' on the CSS (cascading stylesheet) be >> changed. >> >> Since you found the CSS file & section already, please note those to >> minimize the search for the line to be changed. >> >> -Brian >> >> On Fri, Dec 6, 2019 at 9:37, Chris Wood >> <chr...@gm...> wrote: >> >> -- >> Gramps-users mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-users >> https://gramps-project.org > > -- > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > https://gramps-project.org -- --------------------------- Have A Nice Day --------------------------- |
|
From: <Emy...@ya...> - 2019-12-22 01:12:02
|
It isn't actually a font rendering problem or a bug. Opera is just correctly supporting the "font-weight:lighter" property while the other browsers did not. What was described as 'bad font rendering' is a matter of personal opinion. Some people simply don't like that look. But such subjective opinion is why MediaWiki (the engine driving the Gramps wiki) has the option for logged-in users to select themes. You don't need to customize the stylesheets manually. Just become a registered & you can select one of the other 4 standard built-in Themes/Skins in the Appearance tab of its Preferences. (The four themes are Vector, MinervaNeue, MonoBook, & Timeless) Vector is the default theme. (see https://www.mediawiki.org/wiki/Category:All_skins ) -Brian On Saturday, December 21, 2019, 4:56:37 PM CST, Arentas <55...@gm...> wrote: Hi again, I've seen that issue is sorted out. But when looking at the web page again with Firefox it doesn't look like it's done. As before there was in some areas skinny fonts, now all regular font text is in the same state, where thin and greyish. I have a screenshot attached in this link to comparison to Opera browser https://susepaste.org/49882991I see that in Grams bug tracker I was suggested to use custom stylesheet for firefox https://gramps-project.org/bugs/view.php?id=11469But I can't understand this as a solved problem. I probably can make the custom look and stuff but this will not solve the problem for other users :))) And in reality I not really care about, I will find out how to read this text. but I thought I will report it as a bug.Cheers. On Sat, 7 Dec 2019 at 17:30, Chris Wood <chr...@gm...> wrote: Done! On Fri, 6 Dec 2019 at 16:44, Emyoulation--- via Gramps-users <gra...@li...> wrote: Or, if it is hard to read in Firefox, you could file a bug report for the website asking that the 'lighter' on the CSS (cascading stylesheet) be changed. Since you found the CSS file & section already, please note those to minimize the search for the line to be changed. -Brian On Fri, Dec 6, 2019 at 9:37, Chris Wood<chr...@gm...> wrote: -- Gramps-users mailing list Gra...@li... https://lists.sourceforge.net/lists/listinfo/gramps-users https://gramps-project.org -- Gramps-users mailing list Gra...@li... https://lists.sourceforge.net/lists/listinfo/gramps-users https://gramps-project.org -- --------------------------- Have A Nice Day ----------------------------- Gramps-users mailing list Gra...@li... https://lists.sourceforge.net/lists/listinfo/gramps-users https://gramps-project.org |
|
From: <Emy...@ya...> - 2019-12-22 13:20:43
|
Thanks for that clarification Chris. His request helped because it gave our webmaster a place to log the results of researching the question. So, when the question pops up again & again, it won't have to be researched again. This enhancement actually isn't Gramps Developer choice either. It's an artifact of the MediaWiki tool that drives the support website. Since the font definition is in the default stylesheet, the work of a manual tweak to that stylesheet would possibly be undone each time there an update for MediaWiki. We COULD create our own stylesheet without the font definition. But that paints us into an Evolutionary deadend. As new stylesheet enhancements are added the MediaWiki via expanding the stylesheet, we wouldn't see those gains. There is discussion on the support boards about this and enhancement ideas about it. (Such as: Stylesheets allow overlaying. So a specific style patch could be applied. But a layering in a Patch management approach would create a Frankenstein's monster... slow & unpredictable.) No solution seems to have garnered enough backing to put it in play. Everybody else is waiting an outcome too. Interestingly, a similar issue applies to the web reports in Gramps. If you don't like how a text element is 'decorated' in the webpages, you can manually tweak the stylesheet. But, the same risk of it being undone or a deadend applies. So most people will wait for a developer decision instead of doing that tweak. -Brian On Sun, Dec 22, 2019 at 6:10, Chris Wood<chr...@gm...> wrote: To be clear, I created a bug report only because I identified what looked like the cause of the issue, and it was suggested that I did this. I agree that it's not a bug, more an enhancement request. The issue is that (to my knowledge) there is no strict definition of "font-weight:lighter". We know intuitively what it means, but not precisely what it should look like. Who is to say, for example, which of Chrome or Firefox has it right? Whilst it looks better in Chrome (and apparently Opera), perhaps Firefox has implemented it the way it was intended, and Chrome not. I'm not sure there is a justification for saying which, if any, is supporting it "correctly". As with many aspects of style sheets, it's a matter of trial and error getting to a result that is visually satisfying, and that ultimately is a matter of personal opinion. This is a battle that web developers have had to deal with for many years - finding an acceptable compromise that works in all major browsers, and if none is possible, then going with the solution that works best for the majority of users. If the Gramps developers have determined that "font-weight:lighter" produces the best outcome for the maximum number of users then they've got it right, and users of Firefox (which includes me by the way) will just have to "suck it up", as my American friends would say. Chris On Sun, 22 Dec 2019 at 01:12, Emyoulation--- via Gramps-users <gra...@li...> wrote: It isn't actually a font rendering problem or a bug. Opera is just correctly supporting the "font-weight:lighter" property while the other browsers did not. What was described as 'bad font rendering' is a matter of personal opinion. Some people simply don't like that look. But such subjective opinion is why MediaWiki (the engine driving the Gramps wiki) has the option for logged-in users to select themes. You don't need to customize the stylesheets manually. Just become a registered & you can select one of the other 4 standard built-in Themes/Skins in the Appearance tab of its Preferences. (The four themes are Vector, MinervaNeue, MonoBook, & Timeless) Vector is the default theme. (see https://www.mediawiki.org/wiki/Category:All_skins ) -Brian |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X