This commit is contained in:
Dan 2018-04-04 21:34:11 +02:00 коммит произвёл GitHub
Родитель f95e2eb82c
Коммит 00da1734d4
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4AEE18F83AFDEB23
1 изменённых файлов: 2 добавлений и 2 удалений

Просмотреть файл

@ -20,7 +20,7 @@ All of the C++ code that supports the complex logic of loading and merging overl
XUL Maintainers (Neil Deakin, Gijs Kruitbosch), Firefox Frontend (Dave Townsend)
## Brief
A detailed review of XUL overlay usage shows some common patterns and gives insight into how they can be removed. In general, the uses fall into four categories: unused, used once, used multiple times for simple templating, and used multiple times in a more complicated manor.
A detailed review of XUL overlay usage shows some common patterns and gives insight into how they can be removed. In general, the uses fall into four categories: unused, used once, used multiple times for simple templating, and used multiple times in a more complicated manner.
### Unused
@ -38,6 +38,6 @@ These can be included via the preprocessor.
These are more tricky and will have to be replaced case by case. A few possible approaches:
* Preprocessor include - break up the overlay into a few include files. This has the downside that the master document would need to do a number of includes to get all the various files (dtd, css, js, xml).
* Preprocessor include - break up the overlay into a few include files. This has the downside that the master document would need to do a number of includes to get all the various files (dtd, css, js, xml).
* Custom element - use the new custom elements. The master document would need to includes a JS file that defines the element.
* JS - move element creation to JS