Shiira microsoft how to#
Shiira microsoft software#
Shiira microsoft mac#
Shiira microsoft windows#

After that, MacBU concentrated once again on the next Office release, and MacIE has been well and truly and permanently dead ever since. MSN-for-MacOSX went ahead, and was also critically acclaimed, but once released, indications were that the number of users was about the same as the number of developers. And the week after that, after confirming it with Bill Gates, who was reportedly sad but understanding of the decision, MacIE was officially shut down. A week later we had a meeting with high-up people at Apple, where they told us they were doing a browser. But a meeting was held internally, the outcome of which was that it didn't make sense to build our own browser if Apple was going to bundle one, because the marketshare and mindshare of the distant-second-place browser, on the distant-second-place platform, wasn't worth pursuing.

Shiira microsoft mac#

It got a firm OS X-only foundation, a new even more complient browser base, and then suddenly it became apparent that Apple was doing their own browser, because, well, there were lots of small clues, but the big clues was that Apple had started calling the old Mac IE team offering them jobs.īy that time the Mac division had formally committed to MSN-for-Mac-OSX, so it's not like we were completely going to stop work. So later, when that particular set-top box got cancelled, the IE team got redployed for other WebTV work, and since this was now out of MacBU's control, nothing could really be done.ģ or 4 years went by before enough people in the Mac division wanted to resume work on IE, and when it looked like we might actually need the technology, as a base for MSN-for-Mac, the IE 6 team was formed. The problem with that notion was that WebTV, the team's new bosses, had no reason to actually schedule any time for real IE work. The notion at the time was that the team would continue to do MacIE work in their spare time, since IE 5 was the leader among Mac browsers and no longer needed a full-time team. MacIE 5 was an awesome release, critically aclaimed and everything, with a good development team and a strong testing team, that included daily performance measurement.Īnd yet, almost immediately after 5.0 was released, the MacIE team was redeployed to work on a set-top DVR box. MacIE had one of the strangest and saddest histories I've seen, of any product. Of course, these are only my opinions and do not officially represent the views or practices of my employer. Besides, it's much easier and cheaper for a bank's web team to design with accessability and browser compatibility in mind up front than do a bunch of back-porting and fixing when the customer complaints start rolling in - or worse, when the customer lawsuits start coming! Most banks I deal with also now hire external services to audit their sites for accessability. There are certain laws that have been applied to banking websites, such as the Americans with Disabilities Act and other anti-discrimination laws. Additionally, we certify our site uses 100% W3C DTD-compliant DHTML and is fully accessable by users with disabilities.

Shiira microsoft windows#

While I can only speak for my employer, we test against IE for Windows and Mac OS, Firefox on Windows, Mac OS, and Linux, Safari, and Opera on Windows, Mac OS, and Linux.

Shiira microsoft software#

There are significant regulations and compliance issues that arise with public software testing, including the website. I am a VP at top 5 US bank, and I used to lead the team that develops our public website. It will keep the Mozilla folks on their toes and get them to fix some really nasty problems like memory leaks.Īctually, this is somewhat incorrect. That being said, we would like to support another browser in the Linux/Mac space if possible. I don't want to give 100% of the people a crappy UI because 0.001% of my potential market doesn't support a feature. Of course it's in our best interest to support the widest possible audience, but you have to weigh that off against the richness of the experience. I hate web sites telling me I can't use the UA of my choice.Īnd I hate the two guys that use Billy-Bobs-Web-Browser-That-He-Wrote-In-A-Weekend telling me that I should support his browser. Which browser complies with the standards, or do they both? Well, that's anybody's guess. Go to the home page in IE and Firefox and see how the left nav behaves differently when you hover over an element. For example, is padding included in the width of an element, or not? It depends on whether you're using IE or Mozilla.

Shiira microsoft how to#

Standards are often silent on lots of details, and it's really up to the browser devs on how to do an implementation.