Currently NavigationTiming only records the user's Country. In order to narrow down the metrics to a state-level, we also need to record state/region.
|Resolved||• Gilles||T101345 [DRAFT] Performance Team Goals July - September 2015 (Q1 2015/2016)|
|Resolved||• Gilles||T101819 Track state (region)|
|Resolved||ori||T103720 parsing legacy GeoIP cookies fails (no regex match), enwiki geonotice broken for users with those legacy cookies|
- Mentioned In
- T103720: parsing legacy GeoIP cookies fails (no regex match), enwiki geonotice broken for users with those legacy cookies
rENTI5defbcbe8b17: Record region when available
rMWb28ba8cab1ba: Updated mediawiki/core Project: mediawiki/extensions/NavigationTiming…
rENTIdf0b6b51d817: Record region when available
rMEXT2ec57a13fd2e: Updated mediawiki/extensions Project: mediawiki/extensions/NavigationTiming…
rECNOc7cb171dd45c: Parse region in geoip cookie
rMEXT73fc31545382: Updated mediawiki/extensions Project: mediawiki/extensions/CentralNotice…
rECNOd24bbd0411ec: Parse region in geoip cookie
rOPUPb82bff447b8e: Report IP's region code in geoiplookup
- Mentioned Here
- T102848: Split GeoIP into a new component
If window.Geo is used outside CentralNotice, should we perhaps move the code that deals with it somewhere else? BTW, now would be a great time to do so, since I'm refactoring bannerController just now... Thanks!!
+1 to what @AndyRussG said, this raises already existing red flags for me. Considering how important the Varnish optimization is to us, and that CN is using *only* the country information from the GeoIP cookie, the encapsulation and coupling are becoming increasingly wrong.
Creating new task T102848 to track this.