3.0 upgrade guide doesn't mention changes to `jQuery.parseHTML()`
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 79
- Forks
- 100
- PR merge metrics
- No merged PRs in 30d
Description
As noted in the API documentation, the behavior of jQuery.parseHTML() changed to have the context default to a new document. This is not mentioned in the upgrade guide and has caused confusion for users. See https://bugs.jqueryui.com/ticket/15147 for an example of a user being caught off-guard by this change.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the 3.0 upgrade guide and compare it with the jQuery.parseHTML() API documentation linked in the issue. Document that the context now defaults to a new document and explain the behavior change; done when the upgrade guide clearly covers this user-impacting difference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jquery
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100