235
edits
User:Mnyromyr: Difference between revisions
Jump to navigation
Jump to search
add syncing as option #5
No edit summary |
(add syncing as option #5) |
||
| Line 30: | Line 30: | ||
<ul>This will keep all /xpfe chrome://global/content/bindings/* references intact while using unchanged /toolkit bindings as a base.</ul> | <ul>This will keep all /xpfe chrome://global/content/bindings/* references intact while using unchanged /toolkit bindings as a base.</ul> | ||
Currently, I see only 4. as a useful way to make /xpfe bindings be based upon /toolkit | 5. Just keep /xpfe in sync with /toolkit by backporting interesting stuff | ||
<ul>While this is the easiest way with regard to infrastructural changes, it may be quite tedious to watch out for changes in /toolkit files. | |||
Currently, I see only 4. as a useful way to make /xpfe bindings be based upon /toolkit --- if possible at all (and that still needs some exploring). After all, we can still go for 5. and take the risk of "being behind"... | |||