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
It might appear from this piece of code's existence that New XKit notifies users when a new extension version is available. (I was looking into this to potentially delay it by, oh, 24 hours, so that in most cases users with automatic updates on would not see it frequently if we push updates).
It appears, though, that this piece of code is not called. (Also, I'm pretty sure it would be broken in certain cases if it was called, as per its "This is awful but at least it works" comment; it should be updated to have equivalent comparison logic to the shouldUpdate function in XKit Updates if we enable it. 7.11.0 is currently parsed as older than 7.10.10, if I understand correctly.)
Per git bisect, it appears to have been disabled in #1548 and the comment vanished in #1775.
This is more a "document the situation" issue than a "we should fix this" issue.
It might appear from this piece of code's existence that New XKit notifies users when a new extension version is available. (I was looking into this to potentially delay it by, oh, 24 hours, so that in most cases users with automatic updates on would not see it frequently if we push updates).
It appears, though, that this piece of code is not called. (Also, I'm pretty sure it would be broken in certain cases if it was called, as per its "This is awful but at least it works" comment; it should be updated to have equivalent comparison logic to the
shouldUpdate
function in XKit Updates if we enable it. 7.11.0 is currently parsed as older than 7.10.10, if I understand correctly.)Per git bisect, it appears to have been disabled in #1548 and the comment vanished in #1775.
This is more a "document the situation" issue than a "we should fix this" issue.
XKit/Extensions/xkit_preferences.js
Lines 347 to 390 in 43e5e17
The text was updated successfully, but these errors were encountered: