2015-07-27 17:18:44 +00:00
|
|
|
{
|
|
|
|
|
"name": "CookieWarning",
|
Move the warning outside sitenotice, tidy up code
There's a lot of things going on here, so a quick summary:
* Moved the warning outside sitenotice to avoid reflows and all
kinds of other issues, including those with dismissable notices.
* Placed the warning on the bottom of the page, on all skins, for
consistency and to avoid obstructing vital UI elements such as
site name, user tools, search box.
* Changed the UI to use OOUI for, again, consistency and to avoid
reinventing the wheel with button styling.
* Removed the cookie emoji as it was only taking up valuable space
on mobile and making designing a sensible layout much harder.
* Merged the mobile and desktop RL modules into a single, responsive
one. The warning will work correctly for any skin and screen width.
* The integration tests are truly horrible, I tried to at least
make them work. They deserve a proper rewrite, but that should be
done after the extension switches to the new hook system.
I will post screenshots of this in action in the first of the linked
tasks.
Bug: T271047
Bug: T173335
Change-Id: I6e2a3d7aeccc0d4df1b3238e52c67e72099d27d8
2021-02-01 09:54:49 +00:00
|
|
|
"version": "0.3.0",
|
2015-07-27 17:18:44 +00:00
|
|
|
"author": [
|
Add option to limit the cookie warning to specific regions
With this change, CookieWarning gets two new ways to limit the warning
bar to users of specific (configurable) regions. Based on the geo location
service (which can be configured, too, defaults to freegeoip.net), the
extension will try to get the region of the user (based on the IP address)
and checks it against the configured regions.
With the configuration variable $wgCookieWarningGeoIPLookup, the wiki sysadmin
can configure, if the lookup should be done with PHP (the timeout for the
request is hardcoded to 2 sedonds max), which will save the paylod sent to
the user, or with JavaScript, which will be asynchronous.
Deactivating this feature is easily done by simply setting the configured regions
to false, instead of an object.
Bug: T145780
Change-Id: I4d9371b8608ef270c11c42bdb3a773675977ab3a
2016-09-16 19:18:49 +00:00
|
|
|
"Florian Schmidt",
|
|
|
|
|
"Liz Lee",
|
Move the warning outside sitenotice, tidy up code
There's a lot of things going on here, so a quick summary:
* Moved the warning outside sitenotice to avoid reflows and all
kinds of other issues, including those with dismissable notices.
* Placed the warning on the bottom of the page, on all skins, for
consistency and to avoid obstructing vital UI elements such as
site name, user tools, search box.
* Changed the UI to use OOUI for, again, consistency and to avoid
reinventing the wheel with button styling.
* Removed the cookie emoji as it was only taking up valuable space
on mobile and making designing a sensible layout much harder.
* Merged the mobile and desktop RL modules into a single, responsive
one. The warning will work correctly for any skin and screen width.
* The integration tests are truly horrible, I tried to at least
make them work. They deserve a proper rewrite, but that should be
done after the extension switches to the new hook system.
I will post screenshots of this in action in the first of the linked
tasks.
Bug: T271047
Bug: T173335
Change-Id: I6e2a3d7aeccc0d4df1b3238e52c67e72099d27d8
2021-02-01 09:54:49 +00:00
|
|
|
"Jack Phoenix",
|
|
|
|
|
"Ostrzyciel"
|
2015-07-27 17:18:44 +00:00
|
|
|
],
|
2018-08-02 18:56:24 +00:00
|
|
|
"url": "https://www.mediawiki.org/wiki/Extension:CookieWarning",
|
2015-07-27 17:18:44 +00:00
|
|
|
"descriptionmsg": "cookiewarning-desc",
|
|
|
|
|
"type": "other",
|
2016-01-10 17:58:21 +00:00
|
|
|
"license-name": "MIT",
|
2018-03-22 19:35:37 +00:00
|
|
|
"requires": {
|
2020-03-14 09:01:36 +00:00
|
|
|
"MediaWiki": ">= 1.35.0"
|
2018-03-22 19:35:37 +00:00
|
|
|
},
|
2015-07-27 17:18:44 +00:00
|
|
|
"MessagesDirs": {
|
|
|
|
|
"CookieWarning": [
|
|
|
|
|
"i18n"
|
|
|
|
|
]
|
|
|
|
|
},
|
|
|
|
|
"Hooks": {
|
Move the warning outside sitenotice, tidy up code
There's a lot of things going on here, so a quick summary:
* Moved the warning outside sitenotice to avoid reflows and all
kinds of other issues, including those with dismissable notices.
* Placed the warning on the bottom of the page, on all skins, for
consistency and to avoid obstructing vital UI elements such as
site name, user tools, search box.
* Changed the UI to use OOUI for, again, consistency and to avoid
reinventing the wheel with button styling.
* Removed the cookie emoji as it was only taking up valuable space
on mobile and making designing a sensible layout much harder.
* Merged the mobile and desktop RL modules into a single, responsive
one. The warning will work correctly for any skin and screen width.
* The integration tests are truly horrible, I tried to at least
make them work. They deserve a proper rewrite, but that should be
done after the extension switches to the new hook system.
I will post screenshots of this in action in the first of the linked
tasks.
Bug: T271047
Bug: T173335
Change-Id: I6e2a3d7aeccc0d4df1b3238e52c67e72099d27d8
2021-02-01 09:54:49 +00:00
|
|
|
"SkinAfterContent": "CookieWarning\\Hooks::onSkinAfterContent",
|
2018-07-19 10:48:17 +00:00
|
|
|
"GetPreferences": "CookieWarning\\Hooks::onGetPreferences",
|
|
|
|
|
"BeforeInitialize": "CookieWarning\\Hooks::onBeforeInitialize",
|
Move the warning outside sitenotice, tidy up code
There's a lot of things going on here, so a quick summary:
* Moved the warning outside sitenotice to avoid reflows and all
kinds of other issues, including those with dismissable notices.
* Placed the warning on the bottom of the page, on all skins, for
consistency and to avoid obstructing vital UI elements such as
site name, user tools, search box.
* Changed the UI to use OOUI for, again, consistency and to avoid
reinventing the wheel with button styling.
* Removed the cookie emoji as it was only taking up valuable space
on mobile and making designing a sensible layout much harder.
* Merged the mobile and desktop RL modules into a single, responsive
one. The warning will work correctly for any skin and screen width.
* The integration tests are truly horrible, I tried to at least
make them work. They deserve a proper rewrite, but that should be
done after the extension switches to the new hook system.
I will post screenshots of this in action in the first of the linked
tasks.
Bug: T271047
Bug: T173335
Change-Id: I6e2a3d7aeccc0d4df1b3238e52c67e72099d27d8
2021-02-01 09:54:49 +00:00
|
|
|
"BeforePageDisplay": "CookieWarning\\Hooks::onBeforePageDisplay",
|
2018-07-19 10:48:17 +00:00
|
|
|
"ResourceLoaderGetConfigVars": "CookieWarning\\Hooks::onResourceLoaderGetConfigVars"
|
2015-07-27 17:18:44 +00:00
|
|
|
},
|
|
|
|
|
"config": {
|
2015-08-16 10:00:33 +00:00
|
|
|
"CookieWarningEnabled": false,
|
Add option to limit the cookie warning to specific regions
With this change, CookieWarning gets two new ways to limit the warning
bar to users of specific (configurable) regions. Based on the geo location
service (which can be configured, too, defaults to freegeoip.net), the
extension will try to get the region of the user (based on the IP address)
and checks it against the configured regions.
With the configuration variable $wgCookieWarningGeoIPLookup, the wiki sysadmin
can configure, if the lookup should be done with PHP (the timeout for the
request is hardcoded to 2 sedonds max), which will save the paylod sent to
the user, or with JavaScript, which will be asynchronous.
Deactivating this feature is easily done by simply setting the configured regions
to false, instead of an object.
Bug: T145780
Change-Id: I4d9371b8608ef270c11c42bdb3a773675977ab3a
2016-09-16 19:18:49 +00:00
|
|
|
"CookieWarningMoreUrl": "",
|
2021-01-05 18:56:21 +00:00
|
|
|
"CookieWarningGeoIPServiceURL": "",
|
Add option to limit the cookie warning to specific regions
With this change, CookieWarning gets two new ways to limit the warning
bar to users of specific (configurable) regions. Based on the geo location
service (which can be configured, too, defaults to freegeoip.net), the
extension will try to get the region of the user (based on the IP address)
and checks it against the configured regions.
With the configuration variable $wgCookieWarningGeoIPLookup, the wiki sysadmin
can configure, if the lookup should be done with PHP (the timeout for the
request is hardcoded to 2 sedonds max), which will save the paylod sent to
the user, or with JavaScript, which will be asynchronous.
Deactivating this feature is easily done by simply setting the configured regions
to false, instead of an object.
Bug: T145780
Change-Id: I4d9371b8608ef270c11c42bdb3a773675977ab3a
2016-09-16 19:18:49 +00:00
|
|
|
"CookieWarningGeoIPLookup": "none",
|
|
|
|
|
"CookieWarningForCountryCodes": {
|
|
|
|
|
"EU": "Europe",
|
|
|
|
|
"AD": "Andorra",
|
|
|
|
|
"AL": "Albania",
|
|
|
|
|
"AT": "Austria",
|
|
|
|
|
"BA": "Bosnia and Herzegovina",
|
|
|
|
|
"BE": "Belgium",
|
|
|
|
|
"BG": "Bulgaria",
|
|
|
|
|
"BY": "Belarus",
|
|
|
|
|
"CH": "Switzerland",
|
|
|
|
|
"CS": "Serbia and Montenegro",
|
|
|
|
|
"CZ": "Czech Republic",
|
|
|
|
|
"DE": "Germany",
|
|
|
|
|
"DK": "Denmark",
|
|
|
|
|
"EE": "Estonia",
|
|
|
|
|
"ES": "Spain",
|
|
|
|
|
"FI": "Finland",
|
|
|
|
|
"FO": "Faroe Islands",
|
|
|
|
|
"FR": "France",
|
|
|
|
|
"FX": "France, Metropolitan",
|
|
|
|
|
"GB": "United Kingdom",
|
|
|
|
|
"GI": "Gibraltar",
|
|
|
|
|
"GR": "Greece",
|
|
|
|
|
"HR": "Croatia",
|
|
|
|
|
"HU": "Hungary",
|
|
|
|
|
"IE": "Ireland",
|
|
|
|
|
"IS": "Iceland",
|
|
|
|
|
"IT": "Italy",
|
|
|
|
|
"LI": "Liechtenstein",
|
|
|
|
|
"LT": "Lithuania",
|
|
|
|
|
"LU": "Luxembourg",
|
|
|
|
|
"LV": "Latvia",
|
|
|
|
|
"MC": "Monaco",
|
|
|
|
|
"MD": "Moldova, Republic of",
|
|
|
|
|
"MK": "Macedonia",
|
|
|
|
|
"MT": "Malta",
|
|
|
|
|
"NL": "Netherlands",
|
|
|
|
|
"NO": "Norway",
|
|
|
|
|
"PL": "Poland",
|
|
|
|
|
"PT": "Portugal",
|
|
|
|
|
"RO": "Romania",
|
|
|
|
|
"SE": "Sweden",
|
|
|
|
|
"SI": "Slovenia",
|
|
|
|
|
"SJ": "Svalbard and Jan Mayen",
|
|
|
|
|
"SK": "Slovakia",
|
|
|
|
|
"SM": "San Marino",
|
|
|
|
|
"UA": "Ukraine",
|
|
|
|
|
"VA": "Holy See (Vatican City State)"
|
|
|
|
|
}
|
2015-07-27 17:18:44 +00:00
|
|
|
},
|
|
|
|
|
"ResourceModules": {
|
|
|
|
|
"ext.CookieWarning": {
|
|
|
|
|
"dependencies": [
|
2015-08-16 09:49:05 +00:00
|
|
|
"mediawiki.api",
|
2018-03-22 19:17:13 +00:00
|
|
|
"mediawiki.cookie",
|
|
|
|
|
"mediawiki.user"
|
2015-07-27 17:18:44 +00:00
|
|
|
],
|
2015-08-16 09:49:05 +00:00
|
|
|
"scripts": "resources/ext.CookieWarning/ext.CookieWarning.js",
|
|
|
|
|
"targets": [
|
|
|
|
|
"mobile",
|
|
|
|
|
"desktop"
|
|
|
|
|
]
|
2015-07-27 17:18:44 +00:00
|
|
|
},
|
|
|
|
|
"ext.CookieWarning.styles": {
|
Move the warning outside sitenotice, tidy up code
There's a lot of things going on here, so a quick summary:
* Moved the warning outside sitenotice to avoid reflows and all
kinds of other issues, including those with dismissable notices.
* Placed the warning on the bottom of the page, on all skins, for
consistency and to avoid obstructing vital UI elements such as
site name, user tools, search box.
* Changed the UI to use OOUI for, again, consistency and to avoid
reinventing the wheel with button styling.
* Removed the cookie emoji as it was only taking up valuable space
on mobile and making designing a sensible layout much harder.
* Merged the mobile and desktop RL modules into a single, responsive
one. The warning will work correctly for any skin and screen width.
* The integration tests are truly horrible, I tried to at least
make them work. They deserve a proper rewrite, but that should be
done after the extension switches to the new hook system.
I will post screenshots of this in action in the first of the linked
tasks.
Bug: T271047
Bug: T173335
Change-Id: I6e2a3d7aeccc0d4df1b3238e52c67e72099d27d8
2021-02-01 09:54:49 +00:00
|
|
|
"styles": "resources/ext.CookieWarning/ext.CookieWarning.less",
|
2015-08-16 09:49:05 +00:00
|
|
|
"targets": [
|
Move the warning outside sitenotice, tidy up code
There's a lot of things going on here, so a quick summary:
* Moved the warning outside sitenotice to avoid reflows and all
kinds of other issues, including those with dismissable notices.
* Placed the warning on the bottom of the page, on all skins, for
consistency and to avoid obstructing vital UI elements such as
site name, user tools, search box.
* Changed the UI to use OOUI for, again, consistency and to avoid
reinventing the wheel with button styling.
* Removed the cookie emoji as it was only taking up valuable space
on mobile and making designing a sensible layout much harder.
* Merged the mobile and desktop RL modules into a single, responsive
one. The warning will work correctly for any skin and screen width.
* The integration tests are truly horrible, I tried to at least
make them work. They deserve a proper rewrite, but that should be
done after the extension switches to the new hook system.
I will post screenshots of this in action in the first of the linked
tasks.
Bug: T271047
Bug: T173335
Change-Id: I6e2a3d7aeccc0d4df1b3238e52c67e72099d27d8
2021-02-01 09:54:49 +00:00
|
|
|
"mobile",
|
|
|
|
|
"desktop"
|
2015-08-16 09:49:05 +00:00
|
|
|
]
|
Add option to limit the cookie warning to specific regions
With this change, CookieWarning gets two new ways to limit the warning
bar to users of specific (configurable) regions. Based on the geo location
service (which can be configured, too, defaults to freegeoip.net), the
extension will try to get the region of the user (based on the IP address)
and checks it against the configured regions.
With the configuration variable $wgCookieWarningGeoIPLookup, the wiki sysadmin
can configure, if the lookup should be done with PHP (the timeout for the
request is hardcoded to 2 sedonds max), which will save the paylod sent to
the user, or with JavaScript, which will be asynchronous.
Deactivating this feature is easily done by simply setting the configured regions
to false, instead of an object.
Bug: T145780
Change-Id: I4d9371b8608ef270c11c42bdb3a773675977ab3a
2016-09-16 19:18:49 +00:00
|
|
|
},
|
|
|
|
|
"ext.CookieWarning.geolocation": {
|
|
|
|
|
"scripts": "resources/ext.CookieWarning.geolocation/cookiePolicy.js",
|
2018-03-22 19:17:13 +00:00
|
|
|
"dependencies": [
|
|
|
|
|
"ext.CookieWarning",
|
|
|
|
|
"jquery.cookie"
|
|
|
|
|
],
|
Add option to limit the cookie warning to specific regions
With this change, CookieWarning gets two new ways to limit the warning
bar to users of specific (configurable) regions. Based on the geo location
service (which can be configured, too, defaults to freegeoip.net), the
extension will try to get the region of the user (based on the IP address)
and checks it against the configured regions.
With the configuration variable $wgCookieWarningGeoIPLookup, the wiki sysadmin
can configure, if the lookup should be done with PHP (the timeout for the
request is hardcoded to 2 sedonds max), which will save the paylod sent to
the user, or with JavaScript, which will be asynchronous.
Deactivating this feature is easily done by simply setting the configured regions
to false, instead of an object.
Bug: T145780
Change-Id: I4d9371b8608ef270c11c42bdb3a773675977ab3a
2016-09-16 19:18:49 +00:00
|
|
|
"targets": [
|
|
|
|
|
"mobile",
|
|
|
|
|
"desktop"
|
|
|
|
|
]
|
|
|
|
|
},
|
|
|
|
|
"ext.CookieWarning.geolocation.styles": {
|
|
|
|
|
"styles": "resources/ext.CookieWarning.geolocation/styles.css",
|
|
|
|
|
"targets": [
|
|
|
|
|
"mobile",
|
|
|
|
|
"desktop"
|
|
|
|
|
]
|
2015-07-27 17:18:44 +00:00
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
"ResourceFileModulePaths": {
|
|
|
|
|
"localBasePath": "",
|
|
|
|
|
"remoteExtPath": "CookieWarning"
|
|
|
|
|
},
|
2018-07-19 10:48:17 +00:00
|
|
|
"AutoloadNamespaces": {
|
|
|
|
|
"CookieWarning\\": "includes/"
|
2015-07-27 17:18:44 +00:00
|
|
|
},
|
|
|
|
|
"ConfigRegistry": {
|
|
|
|
|
"cookiewarning": "GlobalVarConfig::newInstance"
|
|
|
|
|
},
|
2018-07-18 09:50:46 +00:00
|
|
|
"ServiceWiringFiles": [
|
|
|
|
|
"includes/ServiceWiring.php"
|
|
|
|
|
],
|
2015-07-27 17:18:44 +00:00
|
|
|
"manifest_version": 1
|
|
|
|
|
}
|