Page 1 of 1

FW 16.1 - cosmetics

PostPosted: Sun Oct 04, 2015 11:20 am
by wd9895
Hi fvdw, hi Jocko

a cosmetic issue in new FW 16.1

On Firefox 42 (last beta, Windows) the menu color - only on the left side - is white when you open the webinterface. After scrolling the mouse from bottom to top it's blue and remains blue. Closing FF and re-open the webinterface again shows white font on the side.

On IE11 it's no problem.

Re: FW 16.1 - cosmetics

PostPosted: Sun Oct 04, 2015 11:24 am
by Jocko
Hi wd9895,

Thank you for this feedback.

I go to deepen this point but may be also an issue with the beta version.

Re: FW 16.1 - cosmetics

PostPosted: Sun Oct 04, 2015 12:00 pm
by wd9895
Yes, can be true.
But I don't have any other color issues with the FF beta.

Thanks.

Re: FW 16.1 - cosmetics

PostPosted: Sun Oct 04, 2015 12:19 pm
by Jocko
FF42.0b3 issue is more large than the white font color on left menu title.

In my case, only one menu item is visible:
ff42.0b3.jpg

It is hard to understand what happens as if I open my debugger, the rest of left menu becomes visible :crazy

So I can not deepen on this html state.

Note with mobile interface there is no issue.

Re: FW 16.1 - cosmetics

PostPosted: Sun Oct 04, 2015 12:32 pm
by Jocko
Maybe a workaround.

To force FF to refresh the left menu table after loading, the attached file hides the table and quickly displays again.

To test it you need to replace home.php in /usr/htdocs by the attached version.

Later, we need to valid it with the official release 42.0

Note: seems that FF follows the same road as Edge where there are issues when on loading some dynamic HTML elements are created :disapprove

Re: FW 16.1 - cosmetics

PostPosted: Sun Oct 04, 2015 4:31 pm
by wd9895
Hi Jocko,

to me it's not a big issue. If FF is the root cause then we wait for the next realease.
Let's not workaround errors from third party companies.

Re: FW 16.1 - cosmetics

PostPosted: Sat Oct 10, 2015 1:16 pm
by wd9895
Hi Jocko,

the workaround works on IE11 and FF42-B05

Greetz
wd9895

Re: FW 16.1 - cosmetics

PostPosted: Sat Oct 10, 2015 1:52 pm
by Jocko
Hi wd9895,

I understand better why we have this behaviour.

For improvement the loading page speed, it seems that FF does not like to make some additional parsing of the HTML page and if you change dynamically the HTML DOM when it loads the page, FF does not succeed to handle fully the new created HTML objects.

So I removed the js code which occurs this issue and no need to use my workaround.

I go to send your the new files

Nice Saturday

Re: FW 16.1 - cosmetics

PostPosted: Sat Oct 10, 2015 2:09 pm
by wd9895
Okay, I see.

Thank you.