Skip to content
This repository was archived by the owner on Jul 29, 2022. It is now read-only.

.html().text()#36

Closed
davidchambers wants to merge 1 commit intoNicolasCARPi:masterfrom
davidchambers:master
Closed

.html().text()#36
davidchambers wants to merge 1 commit intoNicolasCARPi:masterfrom
davidchambers:master

Conversation

@davidchambers
Copy link

It's quite likely that I'm using the plugin incorrectly, but I've encountered a couple of issues (two sides of the same coin, actually):

  • Editing X&Y populates the input field with X&Y
  • Replacing the text with <b>Z</b> results in a b tag being inserted into the DOM

Is there a way to tell the plugin to pass around plaintext rather than HTML? If not, perhaps my change is useful. Whatever the solution, it should not involve presenting the user with HTML character entities. ;)

…Y` from

appearing in the field as `X&amp;Y`, and to prevent input from being treated
as HTML.
@appel
Copy link

appel commented Apr 7, 2011

davidchambers, thank you a bunch! This solved it for me (for now).

@stof
Copy link

stof commented Apr 27, 2012

any chance for this to be merged ?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"self.innerHTML" should be replaced with "str" over here, as well

@ShadowCat7
Copy link

This was created two years ago and is still not merged. The repo owner should care more about string encoding.

@JZL
Copy link

JZL commented Jul 26, 2013

This whole thing hasnt been updated in years. Search for edit in place
jquery plugin and you'll find more modern ones

Jonah

On Fri, Jul 26, 2013 at 4:56 PM, Lukas Attridge notifications@github.comwrote:

This was created two years ago and is still not merged. The repo owner
should care more about string encoding.


Reply to this email directly or view it on GitHubhttps://github.com//pull/36#issuecomment-21647598
.

nimbleapps pushed a commit to nimbleapps/jquery_jeditable that referenced this pull request Sep 2, 2013
@tannermares
Copy link

@tuupola: Rather than have 300 forks can we get some of these PR's merged or give some other people access to merge. This is a great project and would like to see it updated. This PR is a big fix and should have been merged.

@davidchambers
Copy link
Author

More than 1000 days have passed since I opened this pull request. I don't think it's going to be merged. :\

@prashantchhabra89
Copy link

@davidchambers Thank you so much! 😃

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants

Comments