3 ms·

This was not intentional. We had a very short time to get a prototype out the door & couldn't optimise the best we can.

• detritus 11y ago
  Oh, come on - getting a site to work across more than one browser isn't 'optimising to the best you can', it's just sloppy from the off. - ed Although it does say 'prototype', to be fair. Still... 'grr!'
  • simondlr 11y ago
    To be honest, we were frustrated that it slipped through. As in exactly as you say: it's sloppy and should've really not let this happen. Completely our fault.
    • detritus 11y ago
      Thanks for the response - I'm just keen to see 'how this all works' having read that Guardian article last month. Will keep an eye out..!
  • deleted 11y ago
    [deleted]
  • MrMcDowall 11y ago
    I can see how you would naively assume that it's something to do with some CSS issue, but it's nothing to do with CSS. We're trying to use a brand new technology for the first time using libraries that have just been written, and newsflash not all browsers behave the same way. The browser block is up while we figure out where the cracks are during _this prototype_.
    • detritus 11y ago
      Not sure I specified, but what exactly does 'optimise' imply to you?