RE: [WSG] Outlook 2010

2009-06-24 Thread Michael MD
We have a problem! Outlook 2010, according to Campaign Monitor [1], is going to continue to use the crippled MS Word layout engine. They adopted this as the status quo for Outlook 2007 and promptly set rich email with CSS, etc., back a number of years, and are showing no great sign of diverging

Re: [WSG] Outlook 2010

2009-06-24 Thread Matthew Pennell
On Wed, Jun 24, 2009 at 5:15 AM, Joshua Street josh.str...@gmail.comwrote: We have a problem! Outlook 2010, according to Campaign Monitor [1], is going to continue to use the crippled MS Word layout engine. FixOutlook.org aims to collate the community's discontent with this decision using

Re: [WSG] Outlook 2010

2009-06-24 Thread Nathan de Vries
On 24/06/2009, at 9:58 PM, Matthew Pennell wrote: This is so stupid - the reason that Outlook uses Word instead of a decent rendering engine is because of the same standards advocates complaining so much about IE6 being bundled with Windows! You can't have your cake and eat it too... You

Re: [WSG] Outlook 2010

2009-06-24 Thread Andrew Stewart
Nathan, I think you are slightly missing the point, I for one don't care too hoots if microsoft uses its own rendering engine or not. All I care is that they use one that works and I think this is the main point of the campaign. I pretty much left web design a few years back because I

RE: [WSG] RE: Using background images on submit buttons

2009-06-24 Thread Rachel Radford
Hi Jens, Sorry for replying so late, just wondering if you found a solution? The only things I have found online have been to make .Net produce an input type=image / which isn't ideal (the image is in the HTML, not the CSS), or a Linkbutton to then format with CSS more easily. I believe that

Re: [WSG] Outlook 2010

2009-06-24 Thread Nathan de Vries
On 24/06/2009, at 11:40 PM, Andrew Stewart wrote: I think you are slightly missing the point... You might want to re-read (or read) my email. I was responding to Matthew, who was implying that Microsoft's decision to use Word as the rendering engine was due to Opera's complaint to The

RE: [WSG] Outlook 2010

2009-06-24 Thread Conyers, Dwayne
Michael MD wroted: WHY do I have to stuff around with regedit to be able to do view source in current versions of Outlook? Can you pass on that trick? I would love to be able to view source... -- The generation that took acid to escape reality is now taking antacid to deal with reality

RE: [WSG] RE: Using background images on submit buttons

2009-06-24 Thread Chris Taylor
On Behalf Of Rachel Radford Sent: 24 June 2009 14:51 Subject: RE: [WSG] RE: Using background images on submit buttons I fear the only proper solution while using .Net is for the HTML that is produced to change! Rachel, have you had a look at the CSS control adapters

Re: [WSG] website fonts

2009-06-24 Thread Angus MacKinnon
I have been following this thread with interest. Some fonts are thicker than others. You have character spaceing. For example, Arial Narrow takes up less room than Arial and Arial black. I have come across some low vision individuals that only rquire thicker fonts and a little more spacing

RE: [WSG] website fonts

2009-06-24 Thread Conyers, Dwayne
Angus MacKinnon related: Internet Explorer defaults to a 12 point font and Firefox defaults to a 16 point font. Of course, fonts are adjustable in the browser (with some exceptions for hard coded fonts) so a user's preferences may be an override in many cases. -- I made magic once. Now,

Re: [WSG] Outlook 2010

2009-06-24 Thread Nathan de Vries
On 24/06/2009, at 9:58 PM, Matthew Pennell wrote: ...the reason that Outlook uses Word instead of a decent rendering engine is because of the same standards advocates complaining so much about IE6 being bundled with Windows! Microsoft have since responded to the campaign [1] and thrown this

[WSG] Rendering difference between Strict Transitional doctypes in FF, IE8 Safari

2009-06-24 Thread Damian Edwards
Heya, We've found a really strange issue with some CSS layout when serving a page with XHTML 1.0 Transitional vs. XHTML 1.1 (or XHTML 1.0 Strict), in Firefox 3, Safari IE8. The exact same behaviour is seen using the HTML 4.01 versions of the doctypes too. From what I've