Unable to report private messages as Spam in Twitter app since r283565.
<rdar://86043227>
Created attachment 447025 [details] Patch
Comment on attachment 447025 [details] Patch The original change also changed ResourceHandle. Should we add the linked-on-or-after checks there too?
(In reply to Alex Christensen from comment #3) > Comment on attachment 447025 [details] > Patch > > The original change also changed ResourceHandle. Should we add the > linked-on-or-after checks there too? I'd be tempted to wait until we get a report of breakage in iOS wk1. What do you think?
Comment on attachment 447025 [details] Patch I'm not sure. You make the call.
r=me Does this workflow work in the browser? Seems like it would be broken everywhere if the server were broken.
(In reply to Geoffrey Garen from comment #6) > r=me > > Does this workflow work in the browser? Seems like it would be broken > everywhere if the server were broken. I wasn't able to reproduce the issue in browser, only in the Twitter app.
Committed r286971 (245193@main): <https://commits.webkit.org/245193@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 447025 [details].
Follow-up build fix in <https://commits.webkit.org/r286986>.