Hey,<br><br>On Qui, 8 Mai, 2014 at 11:07 , Carlos Garcia Campos <cgarcia@igalia.com> wrote:<br><blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;"><blockquote> I wrote something exactly like this a while ago, specifically so that
Google would stop misbehaving, so we did have something like this, but
I think it was never ported to WebKit2
</blockquote>
I didn't know it :-P</div></blockquote><div><br></div><div>No worries, I kinda thought I had moved that to WebCore so it could be shared, but I just dreamed of it, I guess =P</div><div><br></div><blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;">Thanks for the pointer. I've wrote a patch, for now it only converts the
latest changes we've made to the UA string as site specific quirks. Do
we still need a specific UA string for google sites now that we don't
have Chromium/Chrome in our UA?
See <a href="https://bugs.webkit.org/show_bug.cgi?id=132681">https://bugs.webkit.org/show_bug.cgi?id=132681</a></div></blockquote><div><br></div><div>I like it, thanks for taking this on! I was pondering the Google thing while I read the patch, I think our best bet is to fake being a WebKit-era Chromium, probably, for now. How does that sound?</div><div><br></div><div>Cheers,</div><div><br></div><div>Gustavo Noronha</div>