OOR-CORS: Fix renderers to check the base::Feature too
In the previous patch, renderers are changed to take a command line flag for deciding OutOfBlinkCors mode. But since the flag is passed by chrome/ code, content_browsertests run without the required flag even when the OOR-CORS is enabled. This potentially affects other chromium content embedders and may cause confusing situations. To solve this problem, I changed to use the combination of a flag and the base::Feature. Fortunately, there are only two call sites in the renderer processes, and it won't be so bothering. This fix failed content_browsertests at linux-oor-cors-rel bot. Bug: 1015289 Change-Id: I8835b0c328e23656114b4dfcb87286f6cd1d5455 TBR: sky@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866372 Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Auto-Submit: Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by:Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#707210}
Showing
Please register or sign in to comment