Fix example of "Datalist (auto complete) - Dynamic" polyfill #9065
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this pull request (PR) do? / Que fait cette demande « pull » (PR)?
Corrects documentation examples of Datalist (auto complete) - Dynamic with correct prefixes that actually return issues. The example code is AJAXing in GitHub issues, filtering against "Plugin: Multimedia player" and "Plugin: Lightbox", but it appears as though the labels today are "Feature: Multimedia player" and "Feature: Lightbox".
I realize this is a minor detail in the grand scheme of things, but as a public servant in what I assume is a common situation of trying to apply a
unstoppablesmall force to an immovable object (i.e. the adoption of modern digital standards in my corner of the public service), these documentation pages actually end up being very useful, authoritative examples.Additional information (optional) / Information additionnelle (optionel)
General checklist / Liste de contrôle générale
I don't actually have a true development environment setup for this kind of work and as such can't actually build the code -- but the scope of code changes is so small, this should hopefully be OK. I'm at least not so crazy to propose these changes without any supporting facts, I have included screenshots below of the JSON returned before & after the URL adjustment.
Related issues / Requêtes associées
I didn't open one separately -- hopefully this is ok.
Screenshots / Captures d'écrans
URLs as used in example today (showing raw to explicitly show empty JSON response):
Before:
After: