Skip to main content
Known Participant
October 30, 2018
Question

fr error

  • October 30, 2018
  • 1 reply
  • 513 views

I know that this error warning doesn't prevent it from working in the browser but is it on the radar to address this issue? I am running Dreamweaver 2019 so was hoping that this sort of error (see also CSS Variables) and non-functioning Real Time Preview would have been sorted out.

Feedback from Adobe would be appreciated on this.

    This topic has been closed for replies.

    1 reply

    pziecina
    Legend
    October 30, 2018

    For css variables and the support of the 'fr' unit, watch for support in the Brackets editor. If it does not implement support, then Dw will not have support, as Dw's code editors support for any w3c spec is dependant on it being implemented in Brackets.

    Legend
    October 30, 2018

    pziecina  wrote

    For css variables and the support of the 'fr' unit, watch for support in the Brackets editor. If it does not implement support, then Dw will not have support, as Dw's code editors support for any w3c spec is dependant on it being implemented in Brackets.

    I tend to look beyond these 'warnings' and 'errors' and just treat them as maybe being helpful rather than anything set in stone. I've found that each bit of web-editing software seems to have a 'validation' mind of its own - gone are the days when there were just a few senarios to take account of.

    pziecina
    Legend
    October 30, 2018

    osgood_  wrote

    I tend to look beyond these 'warnings' and 'errors' and just treat them as maybe being helpful rather than anything set in stone. I've found that each bit of web-editing software seems to have a 'validation' mind of its own - gone are the days when there were just a few senarios to take account of.

    As the OP said in the other post, 'css variables', they will not use a property unless it does not give a warning.

    I'm going to make a generalised statement now, so I wish to apologise to anyone it does not apply to.

    Dw is not aimed at the pure coder who wishes for up-to-date support, instead it appears to be targeting the type of user who has only a limited requirerment for support beyond what IE8 was capable of, with a very gradual support for anything beyond specs that were introduced after 2009.

    (currently the Dw managment has no idea how modern rwd works, or what users require beyond the above)