https://bugzilla.wikimedia.org/show_bug.cgi?id=44635
--- Comment #3 from Matthew Flaschen <[email protected]> --- Rather than trying to automatically compensate (which could be wonky), what if we allow tours to specify behavior in multiple skins? Tours could keep using the current syntax that just expresses a single string, like: attachTo: '#searchInput', position: 'bottomRight', So it's no more work at first writing a tour. But for multiple skin support, also allow: attachTo: '#searchInput', position: { default: 'bottomRight', monobook: 'right' } We could also support: attachTo: { default: '#searchInput', monobook: '#somethingElse' }, position: { default: 'bottomRight', monobook: 'right' } In some cases, skins have different selectors for the same or equivalent thing. So it seems to make sense to implement both, working the same way. It would first check for an override, but then fall back to to default (so you can customize for anywhere from none to all of the skins). -- You are receiving this mail because: You are on the CC list for the bug. You are watching all bug changes. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
