Details of CSS changes for IE7


Recommended Posts

http://blogs.msdn.com/ie/archive/2006/08/22/712830.aspx

  Quote
We are currently locking down IE7 for shipping and I wanted to give an update on the CSS work that went into IE7. Chris originally outlined our plans for IE7, and we listened to a lot of feedback (blog, connect database, conferences, our WASP partnership etc.) to help us address the most grievous bugs and prioritize which features to put in for IE7. ...

Here is the list of CSS features and changes for IE7:

Bugs we fixed

* All bugs on positioniseverything.net except the ?escaping floats? bug (which is planned for the future)

o Peekaboo Bug

o Internet Explorer and Expanding Box Problem

o Quirky Percentages

o Line-height bug

o Border Chaos

o Disappearing List-Background bug

o Guillotine Bug

o Unscrollable Content bug

o Duplicate Characters Bug

o IE and Italics

o Doubled Float-Margin bug

o Duplicate Indent bug

o Three pixel text jog

o Creeping Text bug

o Missing First letter bug

o Phantom box bug

Details on some of the other bugs (from sources other than the positioniseverything.net list) that we fixed:

* Overflow now works correctly! (That means boxes do not automatically grow any more.)

* Parser bugs: * html, _property and /**/ comment bug

* Select control: CSS style-able and not always on top

* Auto-sizing of absolute positioned element with width:auto and right & left (great for 3 column layouts)

* Addressed many relative positioning issues

* Addressed many absolute positioned issues

* % calculations for height/width for abs positioned elements http://channel9.msdn.com/ShowPost.aspx?PostID=191182

* <?xml> prolog no longer causes quirks mode

* HTML element truly independent of the Body (now gets its own width, height etc.)

* 1 px dotted borders no longer render as dashed

* Bottom margin bug on hover does not collapse margins

* Several negative margin issues fixed

* Recalc issues including relative positioning and/or negative margins are fixed now

* CLSID attribute of <object> tag no longer limited to 128 characters

* :first-letter whitespace bug described in http://blogs.msdn.com/ie/archive/2005/09/02/460115.aspx fixed

* Descendant selector now works properly for grand children when combined with other selectors

* First-line and first-letter now applies when there is no space between word :first-line and opening brace {

* Pseudo-classes now are working as expected if selector is excluded

* The :link selector works now for anchor tag with href set to bookmark

* Addressed !important issues

* PositionIsEverything piefecta-rigid.htm now works

* List-item whitespace bug fixed

* Fixed Absolutely Buggy II

* Absolute positioned elements now use always correct containing block for positioning and size information

* Nested block elements now respect all overflow declarations (hidden, scroll, etc)

* Fixed the opposing offset problem (absolute positioned element whit all four top, bottom left and right are present)

* <a> tags nested within LI elements will no longer add extra bottom margin when hover occurs

* We no longer lose the image aspect ratio on refresh

* Cleaned up our ident parsing according to CSS2.1 rules

* Fixed parsing bugs for multi- class selectors and class selectors that are combined with id selectors

* And many more

We also extended our existing implementations to comply with W3C specifications:

* Enable :hover on all elements not just on <a>

* Background-attachment: fixed works on all elements ? so Eric Meyer?s complexspiral demo works

* Improved <object> fallback

Finally, we added new features from CSS2.1:

* Min/max width/height support (also for images, which did not work in IE7b2)

* Transparent borders

* Fixed positioning support

* Selectors: first-child, adjacent, attribute, child

o A couple of CSS 3 attribute selectors: prefix, suffix and substring since we were working already in the code base (also the general sibling selector)

* Alpha channel PNG support (Not a CSS feature but too important for designers to not call it out J)

Better Standards Support?

But as we?ve been continually reminded, better standards support in IE also means some pages break. As we struggle to balance the needs of our user customers with the desires of web developers, we need your help. The only way for us to continue to improve our standards support is to get your help in changing your sites for IE7. We have provided a set of documentation and tools to help you transition your pages to IE7:

* The IE 7 Readiness Toolkit pulls together documentation, tools, and guidance for developers, testers, and ITPros to prepare sites, extensions and applications for IE 7.

* The Cascading Style Sheet Compatibility in Internet Explorer 7 - documentation on common breaking patterns and techniques you can do to avoid them.

* Developer and ITPro Checklists

* The IE Developer Center is the clearinghouse for all (past and present) IE developer information.

* We have an Application Compatibility Toolkit that logs and identifies changes in behavior due to changes in IE 7 and Vista.

* All of this is wrapped up for you in the Information Index for IE 7.

Finally, as we?ve talked about before, we have a Web Developer Toolbar, which is a great aid during the development and debugging of a website.

We are already planning for the next IE release and will continue down the road of improving our CSS support.

Markus Mielke

Program Manager

Link to comment
https://www.neowin.net/forum/topic/489472-details-of-css-changes-for-ie7/
Share on other sites

Good to see better support. Easiest way to tell how well it works, will be to try it, but I'm going to wait for the final version first.

My main concern is this part;

  Quote
But as we?ve been continually reminded, better standards support in IE also means some pages break. As we struggle to balance the needs of our user customers with the desires of web developers, we need your help. The only way for us to continue to improve our standards support is to get your help in changing your sites for IE7. We have provided a set of documentation and tools to help you transition your pages to IE7:

Surely the best way to make everyones days better is to follow standards completely! Not "struggle to balance".

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • People yearn for the good old days of IRC and truly open Internet, yet are dismissive of modern solutions like ActivityPub (which Mastodon pioneered) and Matrix. Make it make sense.
    • AI judges learn new tricks to fact-check and code better by Paul Hill Image via Pixabay AI researchers and developers are increasingly turning to large language models (LLMs) to evaluate the responses of other LLMs in a process known as “LLM-as-a-judge”. Unfortunately, the quality of these evaluations degrades on complex tasks like long-form factual checking, advanced coding, and math problems. Now, a new research paper published by researchers from the University of Cambridge and Apple outlines a new system that augments AI judges with external validation tools to improve their judgment quality. This system aims to overcome limitations found in both human and AI annotation. Humans face challenges and biases due to time limits, fatigue, and being influenced by writing style over factual accuracy while AI struggles with the aforementioned complex tasks. The Evaluation Agent that the researchers created is agentic so it can assess the response to determine if external tools are needed and utilizes the correct tools. For each evaluation, three main steps are passed through: initial domain assessment, tool usage, and a final decision. The fact-checking tool uses web search to verify atomic facts within a response; code execution leverages OpenAI’s code interpreter to run and verify code correctness; and math checker is a specialized version of the code execution tool for validating mathematical and arithmetic operations. If none of the tools are found to be useful for making judgments, the baseline LLM annotator is used to avoid unnecessary processing and potential performance regression on simple tasks. The system delivered notable improvements in long-form factual checking, with significant increases in agreement with ground-truth annotations across various baselines. In coding tasks, the agent-based approach significantly improved performance across all baselines. For challenging math tasks, the agents improved performance over some baselines, but not all, and overall agreement remained relatively low at around 56%. Notably, the researchers found that in long-form factual responses, the agent’s agreement with ground-truth was higher than that of human annotators. This framework is extensible, so in the future, other tools could be integrated to further improve LLM evaluation systems. The code for the framework will be made open source on Apple’s GitHub, but it isn’t up yet.
    • https://www.neowin.net/news/tags/mastodon/ In short: Federated Twitter (X)
    • Keep in mind it was purchased by an advertising company. I use SearxNG.
    • I am using Waterfox Private Search now that I started using the Waterfox browser on my PC and Android. Both work great* search waterfox net with full stops in between. * I have an issue where making comments on articles on various websites is difficult with Waterfox on Android as it randomly adds spaces and doubles up on text.
  • Recent Achievements

    • Collaborator
      fernan99 earned a badge
      Collaborator
    • Collaborator
      MikeK13 earned a badge
      Collaborator
    • One Month Later
      Alexander 001 earned a badge
      One Month Later
    • One Month Later
      Antonio Barboza earned a badge
      One Month Later
    • Week One Done
      Antonio Barboza earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      588
    2. 2
      ATLien_0
      219
    3. 3
      Michael Scrip
      170
    4. 4
      Xenon
      136
    5. 5
      +FloatingFatMan
      126
  • Tell a friend

    Love Neowin? Tell a friend!