I see that the change is meant for content-embedders to be able to use a feature that Chrome has.
Ideally, Fuchsia WebEngine (and other content-embedders) should be able to choose the features that are included as part of their build, but I don't think we've set up a convention for doing this.
57KB shouldn't be a huge deal for Fuchsia's binary size, and we could look to exclude the feature later in the ongoing binary size reduction efforts.
I'm OK with using the Fuchsia-Binary-Size= footer to bypass the check.
+Zijie He usually makes the call, but he is OOO for a couple of weeks. Tagging
+Sergey Ulanov if you had any thoughts.
Best,
David