Sp-dev-docs: whoops, illegal rule inserted @-o-keyframes animation_5254g4

Created on 17 Jul 2017 · 8Comments · Source: SharePoint/sp-dev-docs

Hi @waldekmastykarz
Hope you are doing good.
All of a sudden we are facing the below issue which is stating:

sp-classic-page-assembly_en-us_1b43b36….js:385 whoops, illegal rule inserted @-o-keyframes animation_5254g4{from{-webkit-transform:translate3d(-10px,0,0);transform:translate3d(-10px,0,0);}to{-webkit-transform:translate3d(0,0,0);transform:translate3d(0,0,0);}}
_insert @ sp-classic-page-assembly_en-us_1b43b36….js:385

Do you have any idea on this .
Any help would be appreciated.

Many Many Thanks

Source

sidjustsid

👍3

Most helpful comment

@waldekmastykarz
I am experiencing this in all the browsers . Even a default web part provided by SharePoint framework is showing this issue.

@vman : I am facing this issue in production as well.

sidjustsid on 24 Jul 2017

👍3

All 8 comments

_sp-classic-page-assembly_en-us_1b43b36….js_ is a script provided with the SharePoint Framework runtime in Office 365. In which browser are you experiencing this issue? Do you have any other web parts on the page?

waldekmastykarz on 23 Jul 2017

I believe this is related to an underlying issue in Office UI Fabric and glamor. More details here: https://github.com/OfficeDev/office-ui-fabric-react/issues/1971

It should only happen in dev builds but not in production.

vman on 23 Jul 2017

@waldekmastykarz
I am experiencing this in all the browsers . Even a default web part provided by SharePoint framework is showing this issue.

@vman : I am facing this issue in production as well.

sidjustsid on 24 Jul 2017

👍3

Getting this issue in the workbench in SPO but not locally. Any news on it?
I'm getting it in a SPFx webpart created using yo @microsoft/sharepoint and added the PnP-JS-Core package but no other changes.

thomas-bak on 23 Aug 2017

Yeah this is an issue with a recent OUIFR upgrade. We have a fix in-progress which will hopefully be released to SPO soon and released as a tooling change in an upcoming drop.

It's an annoying issue, but it's safe to ignore.

iclanton on 31 Aug 2017

Is this fixed? I'm getting this with SPFX React onpremise or is this is only fixed for SPO?

johnfabian on 4 May 2018

Still experiencing the same as @johnfabian on SPFX Webparts deployed to SP Onprem 2016! Are there any news or suggestions what one could do?

mwehnert on 2 Sep 2019

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues