In bug 26175, there was a suggestion to provide some sort of onContentLoad callback for use by gadgets, so that the gadget code can execute after the diff page loads.
Version: unspecified
Severity: enhancement
In bug 26175, there was a suggestion to provide some sort of onContentLoad callback for use by gadgets, so that the gadget code can execute after the diff page loads.
Version: unspecified
Severity: enhancement
a.d.bergi wrote:
I pondered about it, and came to the conclusion that it should not just be an onLoad-, but also an onChange-Event. For example, when I have changed some links I may inform other scripts (like popups) about the change.
Most of these may be new content, changed and/or rendered by the API, but it has not to.
We even could go so far providing these "event-Listeners" as new Hooks for the page load, so that scripts won't have to register twice.
In my opinion, we should pass some arguments to the trigger:
Other scripts can handle the events and react specific to the passed data.
Feel free to file a separate issue with your feature request, but please don't expand the scope of this issue. Thanks.
pdhanda wrote:
RobLa, Do you have an example of a gadget that was affected by bug 26175?
(In reply to comment #3)
RobLa, Do you have an example of a gadget that was affected by bug 26175?
I don't. Perhaps Andreas (andber93@web.de) does?
a.d.bergi wrote:
(In reply to comment #3)
Sorry, I thougt this bug was for a more general request.
(In reply to comment #3)
Do you have an example of a gadget that was affected by bug 26175?
Oh, everything that wants to change the page view or add eventListeners to the page content. And thats a lot:
...
In the official [[de:MediaWiki:Gadgets-definition]]-list also markadmins, screenreader-optimzing, ß -> ss (swiss spelling) and the timezone-converter are harmed.
Not listing any userscripts which have the problem, too.