[wp-trac] [WordPress Trac] #26842: Contenteditable, multiple spaces,  , and U+00A0
WordPress Trac
noreply at wordpress.org
Tue Jan 30 23:45:44 UTC 2018
#26842: Contenteditable, multiple spaces,  , and U+00A0
------------------------------+-----------------------------
Reporter: azaozz | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Future Release
Component: TinyMCE | Version: 4.7
Severity: normal | Resolution:
Keywords: needs-unit-tests | Focuses:
------------------------------+-----------------------------
Comment (by y0uri):
Replying to [comment:33 galbaras]:
> Replying to [comment:31 y0uri]:
> > I agree, just so long as you mean the filter to be manually
implemented when needed (functions.php or plugin), not in core WP. Nbsp's
are rarely a real problem, which this filter can take care of, and they
are used plenty on purpose. As @afraithe mentions, you can't know if it
was intended or not.
> >
> > Looks like the browsers that are causing this issue need to be fixed
(not holding my breath).
>
> It's not a "real problem". What's the harm in an extra white space,
after all.
You'd think so, but the randomly appearing nbsp's were a real problem for
a client. As far as I can tell, it goes like this: They have a WooCommerce
product feed to an aggregator which I guess moderates product descriptions
(post content). Then when my client edited e.g. product prices, nbsp's
would appear in the descriptions and those products would in the next feed
update appear in the aggregator's moderation queue again, without there
being any "real" changes. They didn't like that. I'd rather have the
aggregator change their code to regex replace nbsp's w/ regular spaces,
makes sense to me for their use, but they made it my problem. The
aforementioned filter fixed it, looks like.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/26842#comment:34>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list