The initial value of "clip-path" is set to invalid value "auto", causing the tab to crash if used

Fixed, not yet flighted Issue #8865594

Open new issue

Browse all tracked issues

Details

Author
Martin W.
Created
Sep 12, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
13.10586
Reports
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

– start: Promo Info – Why this bug is important?
We have identified that this bug was promoted based on telemetry data and affects following products failure 7a31d5d7-9157-5139-0f05-fe182ca5c875 impacts Product

                          Text input        
             [10.0.17604.1000](http://watson/Failure?FailureSearchText=7a31d5d7-9157-5139-0f05-fe182ca5c875&MaxRows=100&OSVersion=10.0.17604.1000&DeviceFamily=)                    
    
                    * indicates that we have shown only top 5 reasons
  
  
  
          
      
          
        -- end: Promo Info --                                                                            If you use "clip-path: unset" in you css the hole site stops working. It shows a error page which says that there was an problem when loading the site.

It is one thing if the property is not supported but breaking the hole site is a no go.

I just add a minimal testfile which triggers the error.

Attachments

1 attachment

Comments and activity

  • Microsoft Edge Team

    OSG V. Sep 14, 2016 2016-09-14T13:50:35.907Z

    Changed Assigned To to “Christian F.”

    OSG V. Sep 20, 2016 2016-09-20T07:20:37.177Z

    Changed Assigned To to “Bogdan B.”

    Francois R. Oct 19, 2016 2016-10-19T00:40:58.04Z

    Changed Title from “css "clip-path: unset" breaks hole site” to “css "clip-path: unset" breaks whole site”

    Francois R. Oct 19, 2016 2016-10-19T01:04:42.74Z

    Changed Assigned To from “Bogdan B.” to “Kevin B.”

  • Francois R. Oct 19, 2016 2016-10-19T01:04:42.74Z Microsoft Edge Team

    Thanks, I can confirm the issue. Let me move this to our backlog.

  • Microsoft Edge Team

    Francois R. May 17, 2017 2017-05-17T23:17:17.95Z

    Changed Status

  • Francois R. May 17, 2017 2017-05-17T23:19:45.893Z Microsoft Edge Team

    Actually, instead of duping this to our internal issue, let’s dupe our internal issue to this. Sorry for confusion if you got status update emails in the mean time.

  • Microsoft Edge Team

    Francois R. May 17, 2017 2017-05-17T23:21:46.69Z

    Changed Title from “css "clip-path: unset" breaks whole site” to “The initial value of "clip-path" is set to invalid value "auto", causing the tab to crash if used”

    Francois R. May 17, 2017 2017-05-17T23:21:46.69Z

    Changed Assigned To to “Saqib A.”

    Francois R. May 17, 2017 2017-05-17T23:21:46.69Z

    Changed Status to “Confirmed”

    Amritam S. Jun 14, 2017 2017-06-14T22:58:16.51Z

    Changed Steps to Reproduce

    Kevin B. Jun 15, 2017 2017-06-15T01:11:31.66Z

    Changed Assigned To from “Saqib A.” to “Jacques N.”

    Jacques N. Jun 19, 2017 2017-06-19T22:26:19.923Z

    Changed Status from “Confirmed” to “Fixed”

    pbstools Jul 11, 2017 2017-07-11T06:51:15.01Z

    Changed Status from “Fixed” to “Fixed, not yet flighted”

    MicrosoftUserFeedbackService Jul 11, 2017 2017-07-11T22:10:59.67Z

    Changed Steps to Reproduce

    Amritam S. Jul 11, 2017 2017-07-11T23:47:01.773Z

    Changed Status from “Fixed, not yet flighted” to “Fixed”

    pbstools Jul 12, 2017 2017-07-12T06:19:50.843Z

    Changed Status from “Fixed” to “Fixed, not yet flighted”

    Steven K. Oct 4, 2017 2017-10-04T05:31:04.613Z

    Changed Steps to Reproduce

  • Anonymous Jan 11, 2018 2018-01-11T08:55:02.477Z

    The clip-path issue which is marked as duplicate from this one can be also reproduced for mask-image CSS property. I wonder if this is also fixed or should I open a new issue?

  • Microsoft Edge Team

    Telemetry B. Jan 25, 2018 2018-01-25T20:49:25.58Z

    Changed Steps to Reproduce

    Telemetry B. Jan 27, 2018 2018-01-27T08:43:42.66Z

    Changed Steps to Reproduce

    Telemetry B. Jan 28, 2018 2018-01-28T05:24:32.55Z

    Changed Steps to Reproduce

    Telemetry B. Jan 29, 2018 2018-01-29T07:02:02.1Z

    Changed Steps to Reproduce

    Telemetry B. Jan 30, 2018 2018-01-30T07:05:52.737Z

    Changed Steps to Reproduce

    Telemetry B. Jan 31, 2018 2018-01-31T07:05:16.6Z

    Changed Steps to Reproduce

    Telemetry B. Feb 1, 2018 2018-02-01T06:45:20.663Z

    Changed Steps to Reproduce

    Telemetry B. Feb 2, 2018 2018-02-02T07:38:15.4Z

    Changed Steps to Reproduce

    Telemetry B. Feb 3, 2018 2018-02-03T08:01:52.063Z

    Changed Steps to Reproduce

    Telemetry B. Feb 4, 2018 2018-02-04T07:55:54.267Z

    Changed Steps to Reproduce

    Telemetry B. Feb 5, 2018 2018-02-05T08:09:52.973Z

    Changed Steps to Reproduce

    Telemetry B. Feb 6, 2018 2018-02-06T07:53:41.33Z

    Changed Steps to Reproduce

    Telemetry B. Feb 8, 2018 2018-02-08T06:44:56.14Z

    Changed Steps to Reproduce

    Telemetry B. Feb 9, 2018 2018-02-09T06:53:06.53Z

    Changed Steps to Reproduce

    Telemetry B. Feb 10, 2018 2018-02-10T07:06:03.907Z

    Changed Steps to Reproduce

    Telemetry B. Feb 11, 2018 2018-02-11T07:02:57.55Z

    Changed Steps to Reproduce

    Telemetry B. Feb 12, 2018 2018-02-12T07:19:47.427Z

    Changed Steps to Reproduce

    Telemetry B. Feb 13, 2018 2018-02-13T06:53:36.11Z

    Changed Steps to Reproduce

    Telemetry B. Feb 14, 2018 2018-02-14T07:08:30.09Z

    Changed Steps to Reproduce

    Jeff W. Feb 15, 2018 2018-02-15T00:16:37.2Z

    Changed Assigned To to “Jacques N.”

    Jeff W. Feb 15, 2018 2018-02-15T00:16:37.2Z

    Changed Status from “Fixed, not yet flighted”

    Francois R. Feb 15, 2018 2018-02-15T00:34:07.48Z

    Changed Status to “Fixed, not yet flighted”

    Francois R. Feb 15, 2018 2018-02-15T00:34:30.593Z

    Changed Steps to Reproduce

    Telemetry B. Feb 15, 2018 2018-02-15T07:10:48.407Z

    Changed Steps to Reproduce

    Telemetry B. Feb 16, 2018 2018-02-16T07:11:54.43Z

    Changed Steps to Reproduce

    Telemetry B. Feb 17, 2018 2018-02-17T07:24:38.74Z

    Changed Steps to Reproduce

    Telemetry B. Feb 21, 2018 2018-02-21T10:53:01.95Z

    Changed Steps to Reproduce

    Telemetry B. Feb 24, 2018 2018-02-24T08:58:27.543Z

    Changed Steps to Reproduce

    Telemetry B. Feb 25, 2018 2018-02-25T09:01:42.527Z

    Changed Steps to Reproduce

    Telemetry B. Feb 26, 2018 2018-02-26T08:58:31.363Z

    Changed Steps to Reproduce

    Telemetry B. Feb 27, 2018 2018-02-27T08:50:39.203Z

    Changed Steps to Reproduce

    Telemetry B. Feb 28, 2018 2018-02-28T08:55:23.507Z

    Changed Steps to Reproduce

    Telemetry B. Mar 1, 2018 2018-03-01T21:13:53.23Z

    Changed Steps to Reproduce

    Telemetry B. Mar 2, 2018 2018-03-02T08:45:08.063Z

    Changed Steps to Reproduce

    Telemetry B. Mar 3, 2018 2018-03-03T07:13:30.657Z

    Changed Steps to Reproduce

    Telemetry B. Mar 4, 2018 2018-03-04T07:10:02.397Z

    Changed Steps to Reproduce

    Telemetry B. Mar 5, 2018 2018-03-05T06:56:55.83Z

    Changed Steps to Reproduce

    Telemetry B. Mar 6, 2018 2018-03-06T06:58:08.67Z

    Changed Steps to Reproduce

    Telemetry B. Mar 7, 2018 2018-03-07T06:53:26.903Z

    Changed Steps to Reproduce

    Telemetry B. Mar 8, 2018 2018-03-08T08:34:58.587Z

    Changed Steps to Reproduce

    Telemetry B. Mar 9, 2018 2018-03-09T08:42:04.463Z

    Changed Steps to Reproduce

    Telemetry B. Mar 10, 2018 2018-03-10T08:50:30.91Z

    Changed Steps to Reproduce

    Telemetry B. Mar 11, 2018 2018-03-11T09:00:48.183Z

    Changed Steps to Reproduce

    Telemetry B. Mar 12, 2018 2018-03-12T08:59:06.897Z

    Changed Steps to Reproduce

    Telemetry B. Mar 23, 2018 2018-03-23T01:38:10.37Z

    Changed Steps to Reproduce

    Telemetry B. Mar 23, 2018 2018-03-23T08:47:55.817Z

    Changed Steps to Reproduce

    Telemetry B. Mar 24, 2018 2018-03-24T09:01:22.743Z

    Changed Steps to Reproduce

You need to sign in to your Microsoft account to add a comment.

Sign in