New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The old Outlook.com CSS support depends on case #6

Closed
hteumeuleu opened this Issue Aug 8, 2015 · 2 comments

Comments

Projects
None yet
1 participant
@hteumeuleu
Owner

hteumeuleu commented Aug 8, 2015

Outlook.com filters some properties depending on their case. For example, Outlook.com supports Margin:0; but not margin:0;. I tested every properties based on this list, and 19 properties affected by this behavior. Some will only work when written in lowercase. And others will only work when written in anything but lowercase.

Properties only supported in lowercase :

  • alignment-baseline
  • baseline-shift
  • clip-path
  • color-interpolation-filters
  • flood-color
  • flood-opacity
  • image-rendering
  • lighting-color
  • mask
  • opacity

Properties only supported in anything but lowercase :

  • Float
  • Margin
  • Margin-bottom
  • Margin-left
  • Margin-right
  • Margin-top
  • Outline
  • Position
  • Z-index

@hteumeuleu hteumeuleu added the bug label Aug 8, 2015

@hteumeuleu hteumeuleu changed the title from Outlook.com CSS support depends on case to The old Outlook.com CSS support depends on case Mar 16, 2016

@hteumeuleu

This comment has been minimized.

Show comment
Hide comment
@hteumeuleu

hteumeuleu Mar 16, 2016

Owner

This only happens in the old Outlook.com. The new Outlook.com / Office 365 doesn't have this bug.

Owner

hteumeuleu commented Mar 16, 2016

This only happens in the old Outlook.com. The new Outlook.com / Office 365 doesn't have this bug.

@hteumeuleu

This comment has been minimized.

Show comment
Hide comment
@hteumeuleu

hteumeuleu Jan 30, 2018

Owner

The newer version of Outlook.com doesn't have this bug. The old Outlook.com should be completely obsolete, so I'm closing this bug.

Owner

hteumeuleu commented Jan 30, 2018

The newer version of Outlook.com doesn't have this bug. The old Outlook.com should be completely obsolete, so I'm closing this bug.

@hteumeuleu hteumeuleu closed this Jan 30, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment