Allow user to specify pre-existing container element - #16878
Closed
fractaledmind wants to merge 19 commits into
Closed
Allow user to specify pre-existing container element#16878fractaledmind wants to merge 19 commits into
fractaledmind wants to merge 19 commits into
Conversation
# Conflicts: # awesomplete.js
…parentNode Avoids DOM Error 3
Collaborator
|
Whoa, I think you accidentally included a bunch of unrelated commits? Thanks for sending a PR! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is similar to ##16805, but in-line with the code style and API design of #16787. It is the pair of #16787.
Here we allow the
containerobject to be set using a selector. This also changes the default className for the container [1] to make things a bit more explicit and [2] to make the backwards-compatible CSS possible.