Moonchild wrote:I'm aware of the banner and button -- I have sent them a message about the top bar's forced light grey and teal-blue theme that is applied now being jarring on dark themes and it should follow the color of the background image like it did before.
I do not see any unresponsive scripts, however.
Is it possible that you could please look into why for just Pale Moon (and FF and to some extent Basilisk) it takes many times longer to load the start.me page ever since the new "2018" start.me changes were implemented as of 1-19-18 (at least for what I use in my start.me page) than is the case with other browsers (i.e. Opera, Chrome, IE11 etc)?
I thought you should know this because the new "2018" changes appear to be impacting Pale Moon (and FF as well) by significantly increasing the start.me page load time which appears to be related to specific widgets causing specific script issues. This is a significant issue in my opinion because this involves
the exact same start.me page for all browsers of which only Pale Moon and FF are uniquely impacted by "script busy" issues (in my case) that necessitate a significant change in these two browsers script wait time settings to allow the page to successfully load (see details below).
I have solved the problem of persistent "script busy" errors by having to increase the script wait time by 4X's the default in both Pale Moon and FF (i.e. dom.max_script_run_time for Pale Moon had to be increased from my previous default value "20" to "80") to get Pale Moon past the multiple persistent "script busy" errors (i.e. script errors involving "
https://start.me/assets/application-libraries-......js". These scripts generally take 80-90 seconds to finish which is the reason it is necessary to increase the script wait time by 4 TIMES the default I had before
EVER SINCE THE "2018" CHANGES TO START.ME
released on 1-19-18.
Here are the load times on various browsers (since the "2018" changes to start.me).
Pale Moon: 10-15 seconds at which time there is a hang time of 80-90 seconds until some widgets eventually load successfully.
FF: same as above
Basilisk: 55-65 seconds until fully loaded.
Opera, Chrome, IE11: 17-20 seconds until page is fully loaded.
Since the "2018" change:
For Pale Moon and FF the load time has increased by perhaps 3-4 times.
For Basilisk the load time has increased by perhaps 15-25 seconds at most.
No change for Opera, Chrome, IE11.
All pretty much due to the
start.me "assets/application-libraries" related script.
I am using the most current Java (build 1.8.0_161-b12) and my start.me page consists of 6.5 pages (6.5 clicks in scroll bar to go from top to bottom/bottom to top). I have about 32 modules with links in each module of any where from 10-60 links as well as a few widgets (i.e. Weather, Calendar widgets) which appear to be related to the script issue as observed when the page loads (which involved some of the widgets that eventually do load as a result of significantly increasing the script wait time setting in about:config for both Pale Moon and FF).
I am not getting anywhere with start.me support (refer to previous posts in this topic).
I first reported the issue (in part) to start.me support as such:
.... start.me.... needs to work in Pale Moon and Firefox which it fails to do....
First you need to know that I am using the current Java version 8 update 61 (build 1.8.0_161-b12), which I recently updated to in the past few days. Your tech department should test using the most current Java build.
Here are [examples of] the persistent JavaScript errors....
LINE 2:
https://start.me/assets/application-lib ... 2e28cf4.js
Once past this Java Script error (script has to be stopped) then the DISCOVER WIDGET will render successfully.
LINE 2:
https://start.me/assets/application-lib ... 2e28cf4.js
Once past this Java Script error (script has to be stopped) then the WEATHER WIDGET will render successfully.
It appears there are JS issues in the "assets/application-libraries".....
Please look into this issue.
As to the Banner, it has always displayed as a black banner up until yesterday. Your change is wrong-headed. You need to return to what you had before --- PLEASE!!
As to the "button" at the bottom-right of the start-page, I have to say this is not a good idea either -- access to the these links should not be accessed via a floating button that obscures the page.....
I have since been in contact with
Michiel de Wit and his most recent reply was:
.... about the script issue: our 2018 theme update involves little to no scripting changes, so there might be some other reason. More in general: you might know we are a small organization with a small team. Our product is free to use, so that means our resources are rather finite. That’s why we are not able to offer advanced rollback features or gradual transitions to a new theme: as much as we would like to have such features, ther are simply to costly. At the moment we are investing quite a lot of our time in a very important project that will benefit all users, especially those who use start.me as a start page....
The last reply I got from support was:
Hi,
I believe you may already have been in touch with Michiel....
We have now added the option to choose a different (dark) background color.
Click the edit-icon next to the page title and select "Change background" or "Layout/Theme". Here you can select the color of the header by clicking Dark/Light theme.
Let me know if you have any questions still.
No further reference to the script issues.
Since the recent start.me changes appear to be impacting Pale Moon (at least in my case - and to a lesser extent Basilisk) in significant ways --- is there any way you can try comparison load tests that involves a relatively large start.me page that would include a few widgets (i.e. Weather, Calendar, Discover widgets) in regards to Pale Moon as contrasted to other browsers (i.e. Opera, Chrome, IE11 all of which do not seem to be impacted in the same way). As stated the JS issues in my case appear to involve specifically the "assets/application-libraries" scripts.....
Of course the timing may vary as contrasted to my case but if Pale Moon is "relatively" slower than the other browsers previously referenced that do not seem to be impacted there would presumably be a reason for this that should be looked into it would seem....
:
: 
They say below, the change to the "toolbar" "... becomes "less distracting which allows you to focus on the contents of your page more". WHAT!!!!, IT IS EXACTLY THE OPPOSITE!!!! IT NOW STANDS OUT MORE AND IS AS MOONCHILD STATED FRANKLY "JARRYING...." ON DARK THEMES which is as we know a relatively popular theme (part of the reason I went with start.me is because I was able to integrate the start.me page well with a dark theme --- they have in their infinite wisdom negated that without any option to undo the change --- brilliant!!!)
-bruce /* 
(btw, this load issue is only the case for Pale Moon and FF I might add - others browser have not been impacted for whatever reason)
