The goal is to understand the degree of compatibility of Safari with .aspx services. Is there a comprehensive list of .aspx functionality that fails in Safari? OR

Is there a method \ line of thought to evaluate an .aspx page to determine any functional limits from a Safari perspective?

Although one can simply try the pages in Safari, I am reluctant to try it with this government website:


State of Florida Department of Revenue website for reporting sales tax. The website allows me to login with Safari, but indicates:

This website is optimized for use on a PC using Microsoft Internet Explorer. If you are using any other web browsers, this site may not appear or function as designed. We do not officially support the Macintosh platform.

  • Is that really a government webpage its on a .net domain and your question reads like spam or some other nasty action – mmmmmm Jul 13 '18 at 21:12
  • I believe it actually is a government webpage, although it's remarkably fraudulent looking. – Ezekiel Elin Jul 13 '18 at 22:58
  • In addition to the requirements for how to ask for off-site resources, be sure to remove all but one central question. Asking multiple distinct questions also is reason to put a hold on this question. – bmike Jul 13 '18 at 22:59
  • The webpage redirects to floridareveune.com and is legit. They also say they support Safari: floridarevenue.com/Pages/browser.aspx What is the problem you're having, exactly? – Allan Jul 16 '18 at 18:25
  • Answer to your question: There's no .aspx-specific functionality that fails in Safari. The reason for this is that .aspx is entirely run on the server, not in the browser. The output from that .aspx-page usually contains HTML5 and JavaScript that is used by the browser. Any incompatibility with Safari are then HTML or JavaScript incompatibilities, and thus not specific to .aspx. To sum it up, there's nothing "special" about browsing .aspx pages on Safari compared to browsing any other kind of page such as those generated by PHP, Java, Node.JS or indeed plain HTML. – jksoegaard Jul 16 '18 at 18:37

ASPX is a Server Side Choice

ASPX is a server side technology. The web pages created by ASPX are not inherently limited on Safari browsers.

This is the same for other server side technologies such as Java, php, and perl.

Developer's Responsibility

The developer of the .aspx created page is responsible for producing content that conforms to widely accepted web standards. These standards include HTML5 and those published by the World Wide Web Consortium.

Web developers can refer to resources such as QuirksMode for a guide to what features are supported by which browsers.

Webmasters' Stack Exchange

For help with specific web technologies and choices, please ask on the specialised Webmasters Stack Exchange.

| improve this answer | |

At a high level, I would say there is no generalization you can apply since the .aspx just is the default extension for a specific web framework that runs on the server side. Think of .aspx as the container and not the content of the web page or the languages used.

As an analogy - you could ask if this container has a specific food in it:

enter image description here

Everyone might expect that it’s an Americanized version of fast food that vaguely resembles some street food from China, but it could be anything inside that container and not even food (or standard food for sure).

With JavaScript and some plug in - you could have binary data and not even HTML/CSS being delivered from that site or it could be amazingly standards-compliant and responsive web design.

Note, I haven’t even begun to mention Safari. Other than empirically testing each specific site you want and recording how it functions you’d need to analyze what you feel “compatible” means and then narrow your search for frameworks or tools.

If you wanted a fairly cross-platform web standards, you could do far worse than starting with http://validator.w3.org/

That tool throws 20 errors and 9 warnings against your site but that doesn’t mean Safari can’t do some or all of what it needs.

| improve this answer | |
  • So it is not the .aspx container, but the contents that one should focus upon to understanding compatibility? – gatorback Jul 16 '18 at 20:43

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .