Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Ko téma oñeñongatúma. Ejapo porandu pyahu eikotevẽramo pytyvõ.

CSS/HTML rendering bug

  • 2 Mbohovái
  • 2 oguereko ko apañuãi
  • 3 Hecha
  • Mbohovái ipaháva cor-el

doublecaffe
doublecaffe
more options

I created an HTML/CSS code for rendering some shapes. No Javascript. No images. Just plain HTML/CSS. The result displays a bug in an element, compared with Chrome. This is not the first time I'm getting this kind of errors in Firefox browsers. Other HTML/CSS elements created previously have rendering issues, but they seem fine in other browsers.

You can verify it here: http://codepen.io/doublecaffe/pen/QwmZJB

Image attached. I'm using Firebox v36, Firefox Developer Edition 37.0a2 and Chrome 40.0.2214.115 m. Any clue about this or fix in a future update?

Thx!

I created an HTML/CSS code for rendering some shapes. No Javascript. No images. Just plain HTML/CSS. The result displays a bug in an element, compared with Chrome. This is not the first time I'm getting this kind of errors in Firefox browsers. Other HTML/CSS elements created previously have rendering issues, but they seem fine in other browsers. You can verify it here: http://codepen.io/doublecaffe/pen/QwmZJB Image attached. I'm using Firebox v36, Firefox Developer Edition 37.0a2 and Chrome 40.0.2214.115 m. Any clue about this or fix in a future update? Thx!
Mba’erechaha japyhypyre oñondivegua

Opaite Mbohovái (2)

guigs
guigs
more options

Please also provide this information in a bugzilla issue in this component:

cor-el
cor-el
  • Top 25 Contributor
  • Moderator
more options

Looks fine here in Firefox 36.

You can try to disable OMTC and leave hardware acceleration in Firefox enabled.

  • about:config page: layers.offmainthreadcomposition.enabled = false

You can try to disable hardware acceleration in Firefox.

  • Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"

You need to close and restart Firefox after toggling this setting.