Re: [Fed-Talk] AKO/DKO and Safari 4
Re: [Fed-Talk] AKO/DKO and Safari 4
- Subject: Re: [Fed-Talk] AKO/DKO and Safari 4
- From: Basil Decina <email@hidden>
- Date: Fri, 12 Jun 2009 09:51:49 -0400
Boy, this is an active thread --- almost 20 posts in less than 12
hours !
You would almost think that there are MacOS Safari users who rely on
AKO/DKO and can't get their issues resolved by either the Army (who
are supposed to be promoting standards, not proprietary solutions) or
Apple (who, as "#2", needs to try harder and bring at least some of
ActiveX into Safari --- or at least have one Apple Safari developer
with a CAC who can work with the AKO contractor to come up with work-
arounds). But I digress...
The two main problems I've had which have forced me to abandon Safari
(and Firefox) and use IE under Windows, are:
1) Safari doesn't let one access the Sponsor Management pages. One
needs to log via a CAC to sponsor and approve accounts (which is
reasonable) but for some reason (ActiveX ?) those subpages do not
appear under Safari. (If one clicks on SMC under "My Accounts/
Sponosor Management", one gets a "Please Wait" spinner that never
loads.) I might be able to get to work with FireFox and CoolKey but
I'm trying to be "Apple pure" and not load another CAC management
package (except for those two little non-Apple add-ons called VMware
Fusion and Windows :-)
2) The other major problem is that if one views any group or set of
files that can only display so many items in a list, and therefore
creates "Page n of m" type navigation, one cannot navigate. One sees
the first page but gets a "Please Wait" spinner that never loads.
The above is actually worse under Safari 4 (and I've been running 4
since it first came out in Beta).
Now that we find there are Safari users who can't access AKO/DKO,
should we start a thread on DTS and DBsign ? (No, please... This is
a joke.)
Basil
On Jun 11, 2009, at 7:53 PM, William Cerniuk wrote:
You build it to standards and make allowances for non-standard
browsers or bugs in browsers.
Highly recommend not using the "user-agent" string though to
identify functionality or issues as overall browser issues. This
will break in your code when the browser is fixed/revised. Even
browsers like Internet Explorer have become significantly more
standards compliant as they are revised. There were a fairly large
number of sites that broke when IE 7 came out as they were designed
against IE'isms or using user-agent to handle IE'isms.
The idea is to identify the functionality that has the issue and
then test for that functionality in the user's browser. When that
functionality works improperly, the code forks to handle the
exception. Sooner or later, the code will no longer be executed as
the browser's improve... but at no point will your logic break your
page operation based upon a browser improvement if it is handled
like this. Sites like www.army.mil took this approach and the IE 7
upgrade was a non-event. Other sites and apps, some mission
critical, flopped like dead fish on IE 7.
V/R,
Wm.
On Jun 11, 2009, at 4:20 PM, skyman375 wrote:
Right, which gets back to the discussion of, do you build a site to
be standards compliant, or to meet the peculiarities of the
predominant browser used to access it?
On Thu, Jun 11, 2009 at 14:42, Dave Schroeder <email@hidden>
wrote:
All the Acid3 compliance in the world oesn't do a heck of a lot of
good if a particular web site in question of choice is still broken
with Safari.
- Dave
On Jun 11, 2009, at 1:30 PM, skyman375 wrote:
Safari 4 is 100/100 Acid test compliant; IE, FF, etc. not so much.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Fed-talk mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Fed-talk mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Fed-talk mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden