Is there a reason why the User-Agent: header for chrome includes both
itself and Safari?
Like so:
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US)
AppleWebKit/525.19 (KHTML, like Gecko) Chrome/0.2.153.0 Safari/525.19
I'm sure you guys had a reason for this.
Maximum Compatibility
This was done for compatibility. Unfortunately a lot of web sites look for
safari in the UA string to determine if they should tailor their content
for webkit! It is a very sad state of affairs. All webkit based browsers
(e.g., Omniweb) include safari in their UA strings for this exact reason,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Darin Fisher wrote:
This was done for compatibility. Unfortunately a lot of web sites look
for safari in the UA string to determine if they should tailor their
content for webkit!
All UA strings these days are ridiculous jokes and Chrome just
HLS, sorry but you've missed out on some news.
The free browser is Chromium, 100% open source. (Google Chrome is 95%
open source, surely not free to redistribute, and contains the
spying auto update feature.)
If you want to have a spy-free browser, get Chromium and disable
search and crash
Thanks for your input. :-)
--
On Sep 25, 9:17 am, Simon B. [EMAIL PROTECTED] wrote:
HLS, sorry but you've missed out on some news.
The free browser is Chromium, 100% open source. (Google Chrome is 95%
open source, surely not free to redistribute, and contains the
spying auto update
I experienced the same on machine which was low on memory (256 MB). It
was Windows XP running inside VirtualBox. Now I'm writing this from
Chrome on WinXP, 448 MB RAM and don't have such problems. Interesting.
Paweł
On Sep 25, 3:50 am, if-ifone [EMAIL PROTECTED] wrote:
I think chrome is great!
Hi,
While working on listen_socket module in Linux I stucked in problem where I
am getting this run time error while running unittest
[0925/013325:FATAL:/home/ibrar/chromium/src/base/message_loop.h(451)] Check
failed: MessageLoop::TYPE_IO == loop-type() (2 vs. 0)
Actually this error comes due
my machine memory is 1g xp.
2008/9/25 ph [EMAIL PROTECTED]
I experienced the same on machine which was low on memory (256 MB). It
was Windows XP running inside VirtualBox. Now I'm writing this from
Chrome on WinXP, 448 MB RAM and don't have such problems. Interesting.
Paweł
On Sep 25,
Glad to see progress, keep up the good work.
N
On Tue, Sep 23, 2008 at 12:59, Mike Pinkerton [EMAIL PROTECTED]wrote:
Just wanted to give folks a quick update on the Mac status of
TestShell. This morning we got it fully linking and bringing up a
window. Note that to do this, we had to stub
After deleting all contents under the directory, the build seems to
work now!
Thanks.
On 9월24일, 오후5시55분, Mike Pinkerton [EMAIL PROTECTED] wrote:
Try tossing your src/xcodebuild folder and trying again. The nature of
the DerivedSources in Webkit makes it hard to fully clean a build just
from
I share your frustration ;-)
-darin
On Thu, Sep 25, 2008 at 4:39 AM, Bernd Kreuss [EMAIL PROTECTED]wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Darin Fisher wrote:
This was done for compatibility. Unfortunately a lot of web sites look
for safari in the UA string to determine if
Maybe it would be a good time for someone to write IETF I-D to
proposed a standard and consistency method for detection. Right now,
the best I can tell, the parsing rule of thumb is the last non-
parenthentical name/version pair.
---
Darin Fisher wrote:
I share your frustration ;-)
-darin
Folks,
Chrome does not properly launch registered extensions on the PC.
It wouldn;'t be an issue if the Always Open Files of this type would
work, but it seems this option is useless. Maybe its not implemented.
If someone would so kind to assist and point me in the right direction
for the
Thanks for the report. Could you please file this in the issue tracker?
Erik
On Thu, Sep 25, 2008 at 12:12 PM, HLS [EMAIL PROTECTED] wrote:
Folks,
Chrome does not properly launch registered extensions on the PC.
It wouldn;'t be an issue if the Always Open Files of this type would
work,
Hi all
I talked to evmar on irc, regarding logging of the IRC channels
(#chromium #chromium-dev). He mentioned that he'd like for it to be
discussed in public, before any decisions are made.
The logging is done by http://echelog.matzon.dk/ and is indexed by
google ;)
The primary purpose of
It was done last week.
http://code.google.com/p/chromium/issues/detail?id=2292
Thanks
On Sep 25, 4:36 pm, Erik Kay [EMAIL PROTECTED] wrote:
Thanks for the report. Could you please file this in the issue tracker?
Erik
On Thu, Sep 25, 2008 at 12:12 PM, HLS [EMAIL PROTECTED] wrote:
I personally am for it, but maybe someone can voice the other side.
On Thu, Sep 25, 2008 at 1:45 PM, Matzon [EMAIL PROTECTED] wrote:
Hi all
I talked to evmar on irc, regarding logging of the IRC channels
(#chromium #chromium-dev). He mentioned that he'd like for it to be
discussed in
17 matches
Mail list logo
