Bug 9849 - ajaxWrite: Site check user-agent and does not work
Summary: ajaxWrite: Site check user-agent and does not work
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Evangelism (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL: http://us.ajax13.com/en/ajaxwrite/
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-11 04:36 PDT by David Carson
Modified: 2020-10-23 13:44 PDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Carson 2006-07-11 04:36:27 PDT
Site currently checks user agent string and does not allow you to enter it. Site is similar to www.writely.com
Comment 1 Joost de Valk (AlthA) 2006-07-11 05:17:23 PDT
These guys should be evangelized. Writely is owned by Google, right?
Comment 2 David Carson 2006-07-11 06:56:08 PDT
(In reply to comment #1)
> These guys should be evangelized. Writely is owned by Google, right?
> 
It's actually not Writely - that's a different site and different bug - it's AjaxWrite.com
Comment 3 Mark Malone 2006-09-29 09:17:07 PDT
Mailed Hish asking for a compatibilty status.
Comment 4 David Kilzer (:ddkilzer) 2006-12-13 03:39:48 PST
(In reply to comment #0)
> Site currently checks user agent string and does not allow you to enter it.

Actually, the site checks more than the user agent string as far as I can tell.  Hacking the Safari binary to return a Firefox 2.0 user agent doesn't work.  The site must be checking individual JavaScript properties to determine browser version (in addition or instead of the user agent string).

Testing ajaxWrite is going to require hacking some JavaScript properties in a custom (local) WebKit build, then reducing bugs as they're found (unless the company is willing to put up a "secret" test page to allow WebKit ToT users in to test).

Comment 5 David Kilzer (:ddkilzer) 2006-12-13 04:42:38 PST
(In reply to comment #4)
> Testing ajaxWrite is going to require hacking some JavaScript properties in a
> custom (local) WebKit build, then reducing bugs as they're found (unless the
> company is willing to put up a "secret" test page to allow WebKit ToT users in
> to test).

The check occurs in this bit of JavaScript:

http://app5.ajaxwrite.com/apps/splash.js

However, it appears that ajaxWrite uses XUL technology (specific to Mozilla and Firefox browsers), which means the current implementation will probably never work on Safari.

Comment 6 Robert Blaut 2008-12-23 04:08:22 PST
I'm unable to load the reported site. 
Comment 7 David Kilzer (:ddkilzer) 2008-12-23 13:04:35 PST
Looks like it moved here:  http://us.ajax13.com/en/ajaxwrite/

The "Launch Now!" button still says Safari is unsupported.  (Spoofing as Firefox 2.0.0.x causes a "write.xul" file to be downloaded.)