OXP Mobile First Toolkit

On a desktop it does nothing at all: no requests are made, apart from the overflow report for a logged-in administrator. On a phone it loads a small runtime plus only the modules you switched on, with no dependencies and no framework. Two of them, the iOS input zoom and the vertical fade, are a few lines of CSS printed straight into the page and load nothing at all.

No. Every module that changes how a page renders is gated behind (hover: none) and (pointer: coarse), in the script that decides what to load and again in the CSS. The overflow report is the one thing that also appears on a desktop, and only for a logged-in administrator: it draws a panel over your own page and changes nothing about the page itself.

Keep it. The toolkit detects it and stands down from that one module, so the two never fight. Deactivate it if you would rather manage fixed backgrounds from the toolkit instead.

That is its default: with nothing configured it activates every element on the page that has a hover effect, because the alternative is a module that does nothing until you write a CSS selector. "Only these elements" is how you narrow it: give it a selector such as .card, .tile and the automatic detection switches off entirely, so only what you named is touched.

Almost certainly the effect is defined in a stylesheet served from another domain, such as a CDN. Browsers refuse to let any script read the rules of a cross-origin stylesheet, so the plugin cannot find that rule to mirror it. Serving the stylesheet from your own domain fixes it.

No. It is rendered only for logged-in users who can manage options.

It now ignores any element whose overflow a container already clips or scrolls, because that element cannot make the page drag sideways and listing it was listing a solved problem. If you dismissed it instead, the panel says how many are hidden and offers to show them again; dismissals are remembered per page, in your own browser.

No, and it cannot. No browser on iOS has ever implemented the Vibration API, Chrome and Firefox for iPhone included, since both are Safari underneath. It works on Android in Chrome, Firefox and Samsung Internet. That is why it is off by default and labelled.

Then it is set to the wrong voice for you. At the top of the page there is a bar with three choices: plain, hybrid and technical. Plain never uses a technical term at all. It only changes the words on that screen, so switching between them is free and changes nothing about your site.

That box wants a CSS selector, which is the name a designer gave the element and usually starts with a dot, like .card. A description of the element, however accurate, matches nothing. The plugin now says so when you save something that does not look like a selector. If you do not know the name, leave the box empty: the module finds the elements on its own, which is what it is designed to do.

Not at the moment: it shows on every page. It is worth checking either way, because a fixed bar sitting on top of a Place order button is the most expensive thing this module can do. If the bar is in the way on one page, leave the module switched off on that site until you are sure it is not.