Bartosz Dziewoński 0ac420ecbc Use setExtensionData() instead of marker comments where possible (2/3) ... We started using marker comments (HTML comments with special content inserted into the page) for the reply buttons back in the day, because we needed to indicate their location in the HTML. Later we used the same idea for things which aren't actually tied to a specific location in the HTML, such as boolean data like __DTEMPTYTALKPAGE__. There is a better way to do this. This commit starts reading from ParserOutput::getExtensionData(), which was generated by the previous commit, and should be present in all cached ParserOutput objects by the time we merge this. Bug: T328980 Change-Id: I4bf81ef3fd904f4d920d0756370c9bfa0a10a774		2023-02-11 19:33:20 +00:00
..
DataUpdatesHooks.php	Track callers of parseRevisionParsoidHtml.	2023-01-11 19:01:45 +01:00
EchoHooks.php	Notify users when a topic they are subscribed to is removed from a page	2022-08-25 03:52:58 +02:00
HookUtils.php	Add comments about unwrapping Parsoid sections	2023-01-27 17:07:56 +01:00
InstallerHooks.php	Store permalink data, implement Special:FindComment/GoToComment	2022-08-11 01:19:47 +02:00
MobileHooks.php	Fix '?dtenable=1' on mobile	2022-10-12 23:53:12 +00:00
PageHooks.php	Use setExtensionData() instead of marker comments where possible (2/3)	2023-02-11 19:33:20 +00:00
ParserHooks.php	Remove some redundant PHPDoc comments	2022-11-29 18:47:18 +00:00
PreferenceHooks.php	Remove some redundant PHPDoc comments	2022-11-29 18:47:18 +00:00
RegistrationHooks.php	build: Updating dependencies	2021-07-22 16:29:04 +00:00
ResourceLoaderHooks.php	Remove some redundant PHPDoc comments	2022-11-29 18:47:18 +00:00
TagHooks.php	Convert more self:: to static::	2022-06-14 22:53:00 +01:00