Search Advanced Search
Advanced Search
Advanced Search
- Task
- ·Closed
Before setting hovercards to default for all users (except those who use the navpop gadget) we should This requires: [ ] Users who have HoverCards enabled by the beta features should continue to have them [ ] Exposure of a JavaScript variable for other JavaScript to determine whether Hovercards is enabled is the tangible thing that will make it possible for central notice to detect if the user is in the hovercards bucket or control (regardless of whether user has subsequently enabled hovercards) ...- Task
- ·Closed
# Define and document the set of events that Hovercards should respond to. # The results of `mw.popups.render` may be cached in order to improve rendering performance but the caching behaviour should be distinct from the rendering behaviour. == Considerations # Hovercards T149801). == Acceptance criteria Full requirements at: https://www.mediawiki.org/wiki/Beta_Features/Hovercards ...- Task
- ·Closed
As a data analyst, I want to understand link interaction without and with HoverCards so that I can help inform decisions regarding tuning and rollout of HoverCards. would be eligible for a preview Add these items to the event logging funnel: [x] Page loaded event w/ HoverCards If errored out or timed out instead of rendering [x] What was clicked: destination|settings cog [x] HoverCards work, but it's conceivable there's a service outage for the specific endpoint) [x] Versioning (which Hovercards ...- T142090: Add hover-card like summary (og:description) to open graph meta data printing plain summary
- Task
Hovercards; {F4336339} Whatsapp {F4336368} Google+ {F4336372} =Acceptance criteria = [] A feature We may need to sync with the performance team+ops and let them know we're doing this in case it impacts ... - Task
- ·Closed
Stage 0: Italian, Russian, Greek, Catalan, Hebrew (see [[https://www.mediawiki.org/wiki/Beta_Features/Hovercards The performance on each Wikipedia will be measured and analyzed. original wording of this task, which is as follows, is still relevant but approached the problem from a performance ...- Diffusion Commit
Gadgets are slow, easily broken, poorly maintained, pose security and performance issues, and are not > Also note that this heavily clashes with the Popups/Hovercards extension. between the two is pretty ugly right now, and at some point I imaging that this should be merged with the Hovercards ...- Task
to select the thumb size and quality in this code without extra round-trips would enable interesting performance Good caching of API responses is becoming more pressing as high-traffic features like hovercards (see To avoid performance impacts, all (simple) requests for a thumb of a given size should map to the same This is good for performance (especially without caching), but also means that on-demand generation & Caching could eliminate the performance issue for higher volume installs, or in an appliance container ...- Diffusion Commit
Auditors: chad Improve performance when constructing custom fields for objects Summary: Ref T11404 (I also want to try to make `arc` faster in the next update, and improving Conduit performance helps On my system, this improves performance by 10-15% for `differential.revision.search`. This leads to poor performance of custom fields. See T11404 for discussion. - This may need to be refined eventually to improve performance. ...
Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL