✓ <> changed:

           What    |Removed                     |Added
                 CC|                            |,
                   |                            |
          Component|FlaggedRevs                 |Javascript
            Version|any                         |unspecified
         AssignedTo|       |
            Product|MediaWiki extensions        |MediaWiki

--- Comment #1 from ✓ <> 2010-12-14 20:01:17 UTC ---
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:
* distinguish between content and userinterface (sidebar, header). What about
interwiki and categories?
* selectors for the loaded elements, e.g. an id
* identificator for the script and its function
Other scripts can handle the events and react specific to the passed data.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to