You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well, I'm pretty sure that everyone who is using this extension have recently experienced outages. Those outages are caused when (e.g. Github) change html structure of website without further warning.
I need manually find out how much was html structure changed and then fix it. This can vary from several minutes to several hours (YES, hours, because in GH, you need to use observer to observe DOM changes and listen on pjax events). Most of time, it takes maximum day-two to fix a problem.
But nowdays, we have much bigger problem - publishing an extension to chrome store (which has most users). Since chrome changed privacy & polices of store extensions, reviewing updated extension can take several days to weeks - depends on extension size and size of userbase). During that time, user has still broken extension :(
in short:
Websites can change HTML structure without warning (it takes several hours to realize it)
We need to update extension in order to work with new HTML structure (max day-two)
Publishing extension to chrome store can take several days
So, my idea to prevent further outages is to be able to temporally turn off extension on specific websites without user knowing it or letting him/her to turn off extension on specific websites. This could be also useful for Gitlab users, which can have different Gitlab versions (old self-deployed version).
Extension could check every day / 12 hours remote config (CDN json) if something is broken
Extension should have popup with options to enable/disable icons on specific websites
Well, I'm pretty sure that everyone who is using this extension have recently experienced outages. Those outages are caused when (e.g. Github) change html structure of website without further warning.
I need manually find out how much was html structure changed and then fix it. This can vary from several minutes to several hours (YES, hours, because in GH, you need to use
observer
to observe DOM changes and listen onpjax
events). Most of time, it takes maximum day-two to fix a problem.But nowdays, we have much bigger problem - publishing an extension to chrome store (which has most users). Since chrome changed privacy & polices of store extensions, reviewing updated extension can take several days to weeks - depends on extension size and size of userbase). During that time, user has still broken extension :(
in short:
So, my idea to prevent further outages is to be able to temporally turn off extension on specific websites without user knowing it or letting him/her to turn off extension on specific websites. This could be also useful for Gitlab users, which can have different Gitlab versions (old self-deployed version).
What do you think ?
WIP (popup branch)
The text was updated successfully, but these errors were encountered: