Hey,
On Sex, 9 Mai, 2014 at 1:49 , Martin Robinson
wrote:
On Thu, May 8, 2014 at 11:42 PM, Carlos Garcia Campos
wrote:
I don't understand this, if sites are working with the current UA,
we
just need to make sure we keep using that UA for those specific
sites
that break. It's a matter of
On Thu, May 8, 2014 at 11:42 PM, Carlos Garcia Campos
wrote:
> I don't understand this, if sites are working with the current UA, we
> just need to make sure we keep using that UA for those specific sites
> that break. It's a matter of filing bugs when we detect something is
> broken because of th
El jue, 08-05-2014 a las 12:08 -0700, Martin Robinson escribió:
> On Thu, May 8, 2014 at 9:18 AM, Gustavo Noronha Silva wrote:
> > 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
>
> I think this is the way it went down:
>
>
On Thu, May 8, 2014 at 9:18 AM, Gustavo Noronha Silva wrote:
> 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
I think this is the way it went down:
1. In the beginning, we had our own custom user agent.
2. Gustavo added code
El jue, 08-05-2014 a las 16:15 -0003, Gustavo Noronha Silva escribió:
> Hey,
>
> On Qui, 8 Mai, 2014 at 11:07 , Carlos Garcia Campos
> wrote:
> > I wrote something exactly like this a while ago,
> > specifically so that Google would stop misbehaving, so we
> > did have som
Hey,
On Qui, 8 Mai, 2014 at 11:07 , Carlos Garcia Campos
wrote:
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
I didn't know it :-P
No worries, I kinda
El mié, 07-05-2014 a las 18:27 -0003, Gustavo Noronha Silva escribió:
> Hey,
>
> On Ter, 6 Mai, 2014 at 7:54 , Carlos Garcia Campos
> wrote:
> > My first idea was to keep them static in the source code, similar to
> > plugin quirks, but I agree that information might become obsolete
> > soon.
>
Hey,
On Ter, 6 Mai, 2014 at 7:54 , Carlos Garcia Campos
wrote:
My first idea was to keep them static in the source code, similar to
plugin quirks, but I agree that information might become obsolete
soon.
I wrote something exactly like this a while ago, specifically so that
Google would sto
[Sorry, I misreplied privately, resending]
Hey,
On Seg, 5 Mai, 2014 at 4:43 , Egor Egorov wrote:
Please forgive me for being naive, but if we can identify those sites
in particular, then we might just as well get in touch with their
administrators and ask then to fix it, right?
I guess th
El lun, 05-05-2014 a las 11:32 -0700, Niranjan Rao escribió:
> I like this idea. Right now we pretend we are chromium. Some questions
> do pop in mind.
>
> 1. Not sure what definition of broken is - rendering problems or
> script problems? Other functionality -e.g. local storage/html5
> quirks/dif
I like this idea. Right now we pretend we are chromium. Some questions
do pop in mind.
1. Not sure what definition of broken is - rendering problems or script
problems? Other functionality -e.g. local storage/html5
quirks/differences etc.
2. Where/how will lists be maintained? Given dynamic na
Please forgive me for being naive, but if we can identify those sites in
particular, then we might just as well get in touch with their administrators
and ask then to fix it, right?
I guess the problem lies with sites not known beforehand for user-agent header
sniffing.
--
Egor Egorov
http:
The user agent string is still causing problems in different web sites.
No matter how we change it, there's always a web site broken after the
change. So, I think it's impossible to have a static user agent string
that works for us everywhere.
What do you think about having different user agent s
13 matches
Mail list logo
