locked
CSS rendering issues with WebBrowser.NavigateToString? RRS feed

  • Question

  • (developing for WP8)

    Are there any known rendering issues for the WebBrowser when using NavigateToString? I made a template with inline css that looks correct on an external browser. Then I generate the final web page using that template and the resulting String looks fine when using the HTML visualizer of the debugger but when the page renders, I hit problems like

    * Font size is very small (has to be pulled up to 40 to be readable)

    * Table cellpadding not honored

    * CSS not cascading correctly

    * Missing borders in table cells

    * "leaking" of font sizes

    Any suggestions?

    Tuesday, March 18, 2014 1:34 PM

All replies

  • In the list strangeness : absolute css font sizes changes depending on cell/table width. How is that even possible?
    Tuesday, March 18, 2014 7:07 PM
  • I noticed that

    <meta name="viewport" content="width=device-width, initial-scale=1.0" />

    has an effect on this. Common knowledge I happened to stumble on? ;-)

    Tuesday, March 18, 2014 7:35 PM
  • Still some CSS issues remain. Is the WebBrowser control essentially the same as the IE on the emulator? I see missing CSS effects but when I copy&paste the page to a server and access it with the real IE on the emulator, the CSS looks fine
    Wednesday, March 19, 2014 8:04 AM
  • Monologue continues ;-) If someone stumbles on this thread, apparently

    <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">

    helps with css3 issues

    Wednesday, March 19, 2014 8:13 AM