Only one site is having issues displaying text but it does not happen with IE.
The text is not displaying on one website only and only in one part of the website and it seems to only be one type of text.
http://wol.jw.org/en/wol/h/r1/lp-e
http://wol.jw.org/en/wol/b/r1/lp-e/nwt/E/2013/45/14
It is the Bible and the Bible's text is the only part that is not displaying correctly. I uninstalled and reinstalled.
FF 40 Windows 7 SP1 64Bit
IE displays the same site and pages correctly.
Chosen solution
I'm out of ideas, sorry.
Well, this AM it was still an issue. I did not reboot my computer or do any downloads for FF, nothing. But I opened another FF window and my home page is set to the Daily Text which I had already done this AM and the Text had been 1/2 as it has been. Suddenly out of nowhere the text is fine.
So I will mark this thread resolved and I have no idea would could have resolved it.
Thanks for all your hard work and for all I know the Organization knew of the issue and changed something this AM between the time I first logged on and opened FF until now.
Read this answer in context 👍 0All Replies (7)
Hi LuvFF2, the team that reviews crash reports only contacts you if they need more information to assist the developers in fixing a bug, they don't provide individual support. If you decide you would like us to look at the reports and give you comments, you can post some of the crash report IDs here. (Otherwise, we have no idea which reports are yours.)
jscher2000 said
Hi LuvFF2, the team that reviews crash reports only contacts you if they need more information to assist the developers in fixing a bug, they don't provide individual support. If you decide you would like us to look at the reports and give you comments, you can post some of the crash report IDs here. (Otherwise, we have no idea which reports are yours.)
OK - I will do that if I keep crashing. It has "suddenly" stopped. If it keeps happening I will submit another Q with crashes or find one already open and follow it adding my crash information ID's to it.
But it looks like we are dead ended with working on the text issue. What do you think?
Modified
LuvFF2 said
If it keeps happening I will submit another Q with crashes or find one already open and follow it adding my crash information ID's to it.
Better to start your own new question unless you can see that the "signatures" of the crash reports match up with someone else's.
But it looks like we are dead ended with working on the text issue. What do you think?
I'm out of ideas, sorry.
There is a way to override a website's font selection and use a local font instead so you can at least read the page. You can use the Stylish extension or create a userContent.css file to create a site-specific substitution:
In another thread, a method was proposed to substitute a locally installed font for one specified by a website. You can do that using a custom style rule (either in the Stylish extension or a userContent.css file). Here's an example, using a similarly proportioned font that you probably have on Windows called Bookmark Old Style.
@namespace url(http://www.w3.org/1999/xhtml);
@-moz-document domain("wol.jw.org") {
@font-face { /* Regular */
font-family:'WtClearText';
src: local("Bookman Old Style");
font-weight:500;
font-style:normal
}
@font-face{ /* Bold */
font-family:'WtClearText';
src: local("Bookman Old Style Bold");
font-weight:700;
font-style:normal
}
@font-face{ /* Italic */
font-family:'WtClearText';
src: local("Bookman Old Style Italic");
font-weight:500;
font-style:italic
}
@font-face{ /* Bold Italic */
font-family:'WtClearText';
src: local("Bookman Old Style Bold Italic");
font-weight:700;
font-style:italic
}
}
I use the Stylish extension because it's easy to preview and attach a screen shot of the results.
Since you mentioned that other areas of the site display correctly for you, this may be more trouble than it's worth.
jscher2000 said
LuvFF2 saidIf it keeps happening I will submit another Q with crashes or find one already open and follow it adding my crash information ID's to it.Better to start your own new question unless you can see that the "signatures" of the crash reports match up with someone else's.
But it looks like we are dead ended with working on the text issue. What do you think?I'm out of ideas, sorry.
There is a way to override a website's font selection and use a local font instead so you can at least read the page. You can use the Stylish extension or create a userContent.css file to create a site-specific substitution:
Since you mentioned that other areas of the site display correctly for you, this may be more trouble than it's worth.
I can just use IE if I need the Research Bible. I am thinking that messing around with things only lead to issues down the road and I am not one to do workarounds and patches but let the "powers that be" correct things. I guess keep this thread open so others can go through it and you may see others begin to state they have the same problem
Thanks for trying!
jscher2000 said
LuvFF2 said
I'm out of ideas, sorry.
</blockquote>
Well, this AM it was still an issue. I did not reboot my computer or do any downloads for FF, nothing. But I opened another FF window and my home page is set to the Daily Text which I had already done this AM and the Text had been 1/2 as it has been. Suddenly out of nowhere the text is fine.
So I will mark this thread resolved and I have no idea would could have resolved it.
Thanks for all your hard work and for all I know the Organization knew of the issue and changed something this AM between the time I first logged on and opened FF until now.
Delete
Modified
Seçilmiş Həll
I'm out of ideas, sorry.
Well, this AM it was still an issue. I did not reboot my computer or do any downloads for FF, nothing. But I opened another FF window and my home page is set to the Daily Text which I had already done this AM and the Text had been 1/2 as it has been. Suddenly out of nowhere the text is fine.
So I will mark this thread resolved and I have no idea would could have resolved it.
Thanks for all your hard work and for all I know the Organization knew of the issue and changed something this AM between the time I first logged on and opened FF until now.
Modified