}This would be cleaner in cookie_store, but actual OWNERs are OoO or in Tokyo, which makes review timing a mess...
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
Weird. Speculative fix LGTM, can we add a regression test? I'm fine with doing that in a followup so that this fix can land quicker.
This would be cleaner in cookie_store, but actual OWNERs are OoO or in Tokyo, which makes review timing a mess...
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
Weird. Speculative fix LGTM, can we add a regression test? I'm fine with doing that in a followup so that this fix can land quicker.
I have no idea as to how we ever get in this state, so I can't really guarantee it.
(The reason I am e-mailing this now is that I spent the morning trying, and failed, and figured I should do mitigation somewhat earlier than 5PM on a Friday).
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Speculative fix for another BadMessage class in RCM.
We somehow receive listener add requests with an empty
URL. I am not sure how we get into this state, but reports
in wild and release schedule require a rapid response, so
just ignore this case; that's behaviorally correct anyway.
The origin in the renderer probably isn't opaque since there is
a report on 147.0.7703.0
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |