Comments on: Why Microsoft Expression Web redefines irony

By: Natosha Villena

Natosha Villena — Wed, 06 Jan 2010 16:17:08 +0000

Wow lol totally amazing crazy and huuuuu oh damn, just look at this WYSIWYG web editor, It kicks ass create a free flash website

By: Inetrnet Explorer Users Denied Access to Web Sites

Inetrnet Explorer Users Denied Access to Web Sites — Thu, 26 Feb 2009 17:09:31 +0000

[...] http://shifteleven.com/articles/2006/11/16/why-microsoft-expression-web-redefines-irony [...]

By: Upgrade to Firefox the Better Solution Because IE7 Can Lead to Chaos

Upgrade to Firefox the Better Solution Because IE7 Can Lead to Chaos — Thu, 26 Feb 2009 00:20:44 +0000

[...] http://shifteleven.com/articles/2006/11/16/why-microsoft-expression-web-redefines-irony Wow, this is absolutely devastating! As near as I can tell, the poor guy at Microsoft has been trying to support open standards against management. He doesn’t say much about the history, i.e. the fact that Microsoft didn’t do anything with IE until they were recently forced to by Firefox competition. The feedback is amazing. Example: [...]

By: Anna Ullrich

Anna Ullrich — Sat, 22 Mar 2008 05:04:38 +0000

Hi R O Cox,

I’m on the Expression Web team. In the BETA, you can find that information in the Help under the topic “Add or remove byte order marks” where it provides you with the following 3 sets of procedures. Also note that we have a new forum for Expression Web at http://forums.expression.microsoft.com/en-US/web/threads/

To add or not add a BOM to new documents:
On the Tools menu, click Page Editor Options.

In the Page Editor Options dialog box, on the Authoring tab, under New Documents, under Add a byte order mark (BOM) to new UTF-8 documents with these file extensions, clear the box next to each file extension you do not want to have a BOM.

To add or remove a BOM from an existing page
Open the web page.

Do one of the following:

On the File menu, click Properties.

In Code view, right-click anywhere in the page, and then click Encoding.

In the Page Properties dialog box, on the Language tab, select or clear Include a byte order mark (BOM).

Note:
The option Include a byte order mark (BOM) is not available if Save the document as is not set to Unicode (UTF-8).

To add or remove a BOM from an existing page or other document
Open the document.

In the document, in Code view, right-click anywhere, and then click Encoding.

In the Text File Encoding dialog box, select or clear Include a byte order mark (BOM).

Anna

By: R O Cox

R O Cox — Tue, 05 Feb 2008 17:14:02 +0000

I am new to Expression Web and find it relatively easy to use and for the most part (according Firefox Web Developer) it produces excellent code. One thing that really distresses me is the bug associated with EW’s use of the Bye Order Mark. While I am not and never will be a programmer, I enjoy producing results that meets quality standards. Unless I hack the template/default files, there is no way I can produce a website that meets W3C standards. Not a single similar EW user will ever produce a site that meets those standards. The BOM error will always occur. It is apparent that MS does not want to support PHP or other similar products. I am not sure if this was an oversight or a purposeful deed. The Beta EW apparently had a button to remove the BOM. I simply can’t find it in my version. I have seen it used in an example on an EW tutorial. When you are responsible for more than 77 percent of the browser population and a similar percent of daily use office products you have a responsibility to do the job right. I hope that MS addresses this issue as soon as possible and provides a product that works.

By: Russ Helfand

Russ Helfand — Fri, 04 May 2007 15:03:54 +0000

I would be grateful if you would re-examine and re-assess your analysis of the Microsoft Expression web site, http://www.microsoft.com/expression. I believe you will find that since you published your original observations a great deal has changed. Nearly the whole site is now ported to fairly vanilla ASP.NET (with progressive enhancement from ASP.NET AJAX). I also written the CSS. To my knowledge all of the ASPX pages (not the lingering few MSPX pages) are 100% compliant with XHTML 1.1 standards per validation from the W3.org markup validator. Likewise, I believe all ASPX pages are 100% 508 compliant (based on Cynthia analysis). If you find exceptions, please let me know as I am trying to fix them as I find them so they don’t accumulate.

FYI, I am the guy who wrote the ASP.NET CSS Friendly Control Adapters, http://www.asp.net/cssadapters and am now the web dev for the Expression web site. The past is the past. I wasn’t involved in the work that you evaluated previously (above). I do hope that you are willing to give the site and the product line a fresh look.

It’s completely fair to criticize when things are wrong. It’s also fair to recognize when they quickly get better.

By: JTMS

JTMS — Fri, 08 Dec 2006 13:03:50 +0000

Andrei – they didn’t even have a doctype :-)

By: SF

SF — Fri, 08 Dec 2006 11:45:37 +0000

@d – where’s the irony here? I don’t see this site/page/blog claiming anything about standards-compliance (let alone selling a tool that claims to be industry-leading in that respect), but MS’s index page for a product that claims to do EXACTLY THAT is pretty obviously a piss-poor example of their shoddiness and lack of attention to detail.

By: Andrei

Andrei — Sat, 25 Nov 2006 21:23:40 +0000

Err… The site made “hefty claims about making valid xhtml…”

You validated in HTML 4.01 Transitional

Validating in XHTML 1.0 Strict returns… wait for it… 239 errors.

By: d

Fri, 17 Nov 2006 21:46:33 +0000

Irony, like this page doesnt validate irony