WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
210750
Text manipulation sometimes fails to replace text in title elements
https://bugs.webkit.org/show_bug.cgi?id=210750
Summary
Text manipulation sometimes fails to replace text in title elements
Wenson Hsieh
Reported
2020-04-20 09:47:12 PDT
<
rdar://problem/61066103
>
Attachments
Patch
(8.93 KB, patch)
2020-04-20 10:16 PDT
,
Wenson Hsieh
thorton
: review+
Details
Formatted Diff
Diff
Patch for landing
(8.92 KB, patch)
2020-04-20 12:52 PDT
,
Wenson Hsieh
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Wenson Hsieh
Comment 1
2020-04-20 10:16:37 PDT
Created
attachment 396986
[details]
Patch
Tim Horton
Comment 2
2020-04-20 12:10:11 PDT
Comment on
attachment 396986
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=396986&action=review
> Source/WebCore/editing/TextManipulationController.cpp:481 > + if (replacementTokens.size() > 1 && (!item.element || !canPerformTextManipulationByReplacingEntireTextContent(*item.element)))
What's all the null checking? Didn't we just do this with `element` above? Why not just use that, too?
> Source/WebCore/editing/TextManipulationController.cpp:488 > + if (i)
Sad that we have to avoid range-based for just for this, but alas
Wenson Hsieh
Comment 3
2020-04-20 12:12:53 PDT
Comment on
attachment 396986
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=396986&action=review
>> Source/WebCore/editing/TextManipulationController.cpp:481 >> + if (replacementTokens.size() > 1 && (!item.element || !canPerformTextManipulationByReplacingEntireTextContent(*item.element))) > > What's all the null checking? Didn't we just do this with `element` above? Why not just use that, too?
Good catch! Changed this to just use `element` and avoid the redundant null check.
>> Source/WebCore/editing/TextManipulationController.cpp:488 >> + if (i) > > Sad that we have to avoid range-based for just for this, but alas
:P
Darin Adler
Comment 4
2020-04-20 12:37:36 PDT
Comment on
attachment 396986
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=396986&action=review
>>> Source/WebCore/editing/TextManipulationController.cpp:488 >>> + if (i) >> >> Sad that we have to avoid range-based for just for this, but alas > > :P
I think we should add a StringBuilder feature for appending things with separators. This comes up a *lot*.
> Source/WebCore/editing/TextManipulationController.cpp:489 > + newValue.appendLiteral(" ");
Appending a space is more efficiently done with ' '.
Wenson Hsieh
Comment 5
2020-04-20 12:49:58 PDT
(In reply to Darin Adler from
comment #4
)
> Comment on
attachment 396986
[details]
> Patch > > View in context: >
https://bugs.webkit.org/attachment.cgi?id=396986&action=review
> > >>> Source/WebCore/editing/TextManipulationController.cpp:488 > >>> + if (i) > >> > >> Sad that we have to avoid range-based for just for this, but alas > > > > :P > > I think we should add a StringBuilder feature for appending things with > separators. This comes up a *lot*.
+1 to this. I also looked for a helper somewhere in WTF to join Vector<String> with a separator, but couldn’t find any.
> > > Source/WebCore/editing/TextManipulationController.cpp:489 > > + newValue.appendLiteral(" "); > > Appending a space is more efficiently done with ' '.
Good point — changed to newValue.append(' ');
Wenson Hsieh
Comment 6
2020-04-20 12:52:39 PDT
Created
attachment 397006
[details]
Patch for landing
EWS
Comment 7
2020-04-20 13:19:59 PDT
Committed
r260393
: <
https://trac.webkit.org/changeset/260393
> All reviewed patches have been landed. Closing bug and clearing flags on
attachment 397006
[details]
.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug