Serraniel/AniwatchPlus
Serraniel/AniwatchPlus
1
0
Fork 0
Code Issues 9 Pull requests 8 Packages Projects Releases 10 Wiki Activity

Feature/#19 notifications tab title #31

Merged
kaffem merged 25 commits from feature/#19-notifications-tab-title into develop 2020-10-28 06:46:24 +01:00
Conversation 7 Commits 25 Files changed 4 +4 -4
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files
Showing only changes of commit 08ce64ad8b - Show all commits

8
src/javascript/enhancements/notifications.js
View file

@ -7,7 +7,6 @@ export function init() {
}, ".*"); }, ".*");
core.runAfterPathnameChange(() => { core.runAfterPathnameChange(() => {
console.log('CHANGE')
updateNotificationsInTitle(); updateNotificationsInTitle();
kaffem commented 2020-09-14 00:24:10 +02:00 (Migrated from github.com)
Review
Copy link

Getting the NotificationCount on every pushState event increases the chance of it failing. With this solution it fails for every item of the Community and Anime dropdownmenus. With the old solution it failed when inserting the Count into the title for the stats, jobs, seasonal, airing, random, profile, watchlist and notifications. 10 vs 8 pathnames where it doesn't work.
Furthermore with this solution we run into problems on the profile pathname:
chrome_yyDTOAsutx
We are adding the NotificationCount to the old count whenever we switch from one tab under profile to another; this did not happen with the old solution.

This seems to be related to #42 tho, if you enable Low-end mobile and check the pathnames after visting /home first, you'll see the notification count appear for a while and then disappear once the site is fully shown. With the new solution its definitely because of #42; we are trying to access the menu while the page isn't fully loaded.

Getting the NotificationCount on every pushState event increases the chance of it failing. With this solution it fails for every item of the Community and Anime dropdownmenus. With the old solution it failed when inserting the Count into the title for the stats, jobs, seasonal, airing, random, profile, watchlist and notifications. 10 vs 8 pathnames where it doesn't work. Furthermore with this solution we run into problems on the profile pathname: ![chrome_yyDTOAsutx](https://user-images.githubusercontent.com/29717789/93030124-fe0ef180-f620-11ea-99b3-151a7ed6a99b.png) We are adding the NotificationCount to the old count whenever we switch from one tab under profile to another; this did not happen with the old solution. This seems to be related to #42 tho, if you enable Low-end mobile and check the pathnames after visting /home first, you'll see the notification count appear for a while and then disappear once the site is fully shown. With the new solution its definitely because of #42; we are trying to access the menu while the page isn't fully loaded.
Serraniel commented 2020-09-16 21:36:59 +02:00 (Migrated from github.com)
Review
Copy link

Do you remember how exactly you produced that bug with the number written in the title multiple times? I haven´t seen that yet.

But something else I noticed was the fact, the title seems to be updated by aniwatch after the blue loading bar on the top disappears. This should be investigated as a new opportunity to decide when we update the title and also would fix the current issue, that we just guess a random number to wait until location change before we update the title, which doesn´t always works as the following gif shows:
2020-09-16_21-32-11-463

Do you remember how exactly you produced that bug with the number written in the title multiple times? I haven´t seen that yet. But something else I noticed was the fact, the title seems to be updated by aniwatch after the blue loading bar on the top disappears. This should be investigated as a new opportunity to decide when we update the title and also would fix the current issue, that we just guess a random number to wait until location change before we update the title, which doesn´t always works as the following gif shows: ![2020-09-16_21-32-11-463](https://user-images.githubusercontent.com/8461282/93383974-b7a9d480-f864-11ea-9ec9-8b560256357b.gif)
kaffem commented 2020-09-18 00:30:46 +02:00 (Migrated from github.com)
Review
Copy link

Yeah thats what I meant. Looks like we should not only wait for the popState but also for onload once their preloader is fixed, or wait for the loading bar to disappear(?)

Yeah thats what I meant. Looks like we should not only wait for the popState but also for onload once their preloader is fixed, or wait for the loading bar to disappear(?)
Serraniel commented 2020-10-25 10:57:50 +01:00 (Migrated from github.com)
Review
Copy link

I introduced another observer, which will execute after the blue loading bar in the top disappears. This error seems not to appear any more with that specific change.

I introduced another observer, which will execute after the blue loading bar in the top disappears. This error seems not to appear any more with that specific change.
Serraniel commented 2020-10-25 11:00:43 +01:00 (Migrated from github.com)
Review
Copy link
  • There still is the problem, that some pages have a different loading method where the menu isn´t available directly in the DOM.
- [x] There still is the problem, that some pages have a different loading method where the menu isn´t available directly in the DOM.
Serraniel commented 2020-10-25 11:29:42 +01:00 (Migrated from github.com)
Review
Copy link

I was able to fix this. We started our scripts after the preloader disappeared. We now also wait for the document.readyState to be "complete" so we can ensure everything is loaded correctly, as the preloader disappears to early on some pages.

I was able to fix this. We started our scripts after the preloader disappeared. We now also wait for the `document.readyState` to be `"complete"` so we can ensure *everything* is loaded correctly, as the preloader disappears to early on some pages.
}, ".*"); }, ".*");
} }
@ -15,9 +14,7 @@ export function init() {
function getNotificationCount() { function getNotificationCount() {
if (core.isLoggedIn()) { if (core.isLoggedIn()) {
let menuUserText = document.getElementById('materialize-menu-dropdown').innerText.split('\n')[4]; let menuUserText = document.getElementById('materialize-menu-dropdown').innerText.split('\n')[4];
console.log(menuUserText);
let notificationCount = menuUserText.match(/\d+/)?.[0] ?? 0; let notificationCount = menuUserText.match(/\d+/)?.[0] ?? 0;
console.log(notificationCount);
return notificationCount; return notificationCount;
} else { } else {
return 0; return 0;
@ -28,6 +25,9 @@ function updateNotificationsInTitle() {
let count = getNotificationCount(); let count = getNotificationCount();
if (helper.assigned(count) && count > 0) { if (helper.assigned(count) && count > 0) {
document.title = `(${count}) ${document.title}`; // document.title is updated after the event is triggered, so we delay our title update by a reasonable time
setTimeout(() => {
document.title = `(${count}) ${document.title}`;
}, 100);
} }
} }