(In reply to Nicolas Chevobbe [:nchevobbe][PTO - back on Monday May 13th] from comment #7) > If possible, it would be nice to not return it. For now, I'm filtering the result to only include rules whose parent rule is a `CSSStartingStyleRule` It seems we don't have extra information in the rule node to know if this style rule is in `@starting-style`. I may miss something or need to dig deeper. I could check this later. > Right. I wonder if that could be weird for developers because they won't see the starting-style rules until the transition is triggered, but we might follow up on this Thanks. Resolving it earlier and keeping this value longer need to tweak the framework. We might have to tweak a lot, but we still can follow up on this. > I updated https://phabricator.services.mozilla.com/D209329 and I can see starting style rules in some cases. > It seems that there's something odd with `InspectorUtils.getCSSStartingStyleRules` for transitions triggered before the inspector is opened/registered? > I have this test page https://ffx-devtools-starting-style.glitch.me/ , where I have a few @starting-style applying to the body, the h1 and div > If I inspect the body or the h1, I'm not getting the starting style (which is properly applies, the transition is visible on screen) > The only way I can see the starting style rules is for element that are added while the inspector is already open. > So for my test page, it's visible on divs that are added with the "Add div" button. > > Would you know what's happening? I will check this soon. (Keep my ni until I found the root cause.) Thanks.
Bug 1893409 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Nicolas Chevobbe [:nchevobbe][PTO - back on Monday May 13th] from comment #7) > If possible, it would be nice to not return it. For now, I'm filtering the result to only include rules whose parent rule is a `CSSStartingStyleRule` It seems we don't have extra information in the rule node to know if this style rule is in `@starting-style`. I may miss something or need to dig deeper. I could check this later. > Right. I wonder if that could be weird for developers because they won't see the starting-style rules until the transition is triggered, but we might follow up on this Thanks. Resolving it earlier and keeping this value longer need to tweak the framework. We might have to change a lot, but we still could follow up on this. > I updated https://phabricator.services.mozilla.com/D209329 and I can see starting style rules in some cases. > It seems that there's something odd with `InspectorUtils.getCSSStartingStyleRules` for transitions triggered before the inspector is opened/registered? > I have this test page https://ffx-devtools-starting-style.glitch.me/ , where I have a few @starting-style applying to the body, the h1 and div > If I inspect the body or the h1, I'm not getting the starting style (which is properly applies, the transition is visible on screen) > The only way I can see the starting style rules is for element that are added while the inspector is already open. > So for my test page, it's visible on divs that are added with the "Add div" button. > > Would you know what's happening? I will check this soon. (Keep my ni until I found the root cause.) Thanks.
(In reply to Nicolas Chevobbe [:nchevobbe][PTO - back on Monday May 13th] from comment #7) > If possible, it would be nice to not return it. For now, I'm filtering the result to only include rules whose parent rule is a `CSSStartingStyleRule` It seems we don't have extra information in the rule node to know if this style rule is in `@starting-style`. I may miss something or need to dig deeper. I could check this later. > Right. I wonder if that could be weird for developers because they won't see the starting-style rules until the transition is triggered, but we might follow up on this Thanks. Resolving it earlier and keeping this value longer need to tweak the framework. We might have to change a lot, but we coiuld follow up on this. > I updated https://phabricator.services.mozilla.com/D209329 and I can see starting style rules in some cases. > It seems that there's something odd with `InspectorUtils.getCSSStartingStyleRules` for transitions triggered before the inspector is opened/registered? > I have this test page https://ffx-devtools-starting-style.glitch.me/ , where I have a few @starting-style applying to the body, the h1 and div > If I inspect the body or the h1, I'm not getting the starting style (which is properly applies, the transition is visible on screen) > The only way I can see the starting style rules is for element that are added while the inspector is already open. > So for my test page, it's visible on divs that are added with the "Add div" button. > > Would you know what's happening? I will check this soon. (Keep my ni until I found the root cause.) Thanks.
(In reply to Nicolas Chevobbe [:nchevobbe][PTO - back on Monday May 13th] from comment #7) > If possible, it would be nice to not return it. For now, I'm filtering the result to only include rules whose parent rule is a `CSSStartingStyleRule` It seems we don't have extra information in the rule node to know if this style rule is in `@starting-style`. I may miss something or need to dig deeper. I could check this later. > Right. I wonder if that could be weird for developers because they won't see the starting-style rules until the transition is triggered, but we might follow up on this Thanks. Resolving it earlier and keeping this value longer need to tweak the framework. We might have to change a lot, but I could follow up on this. > I updated https://phabricator.services.mozilla.com/D209329 and I can see starting style rules in some cases. > It seems that there's something odd with `InspectorUtils.getCSSStartingStyleRules` for transitions triggered before the inspector is opened/registered? > I have this test page https://ffx-devtools-starting-style.glitch.me/ , where I have a few @starting-style applying to the body, the h1 and div > If I inspect the body or the h1, I'm not getting the starting style (which is properly applies, the transition is visible on screen) > The only way I can see the starting style rules is for element that are added while the inspector is already open. > So for my test page, it's visible on divs that are added with the "Add div" button. > > Would you know what's happening? I will check this soon. (Keep my ni until I found the root cause.) Thanks.
(In reply to Nicolas Chevobbe [:nchevobbe][PTO - back on Monday May 13th] from comment #7) > If possible, it would be nice to not return it. For now, I'm filtering the result to only include rules whose parent rule is a `CSSStartingStyleRule` It seems we don't have extra information in the rule node to know if this style rule is in `@starting-style`. I may miss something or need to dig deeper. I could check this later. > Right. I wonder if that could be weird for developers because they won't see the starting-style rules until the transition is triggered, but we might follow up on this Thanks. Resolving it earlier and keeping this value longer need to tweak the framework. We might have to change a lot, but yes, we could follow up on this. > I updated https://phabricator.services.mozilla.com/D209329 and I can see starting style rules in some cases. > It seems that there's something odd with `InspectorUtils.getCSSStartingStyleRules` for transitions triggered before the inspector is opened/registered? > I have this test page https://ffx-devtools-starting-style.glitch.me/ , where I have a few @starting-style applying to the body, the h1 and div > If I inspect the body or the h1, I'm not getting the starting style (which is properly applies, the transition is visible on screen) > The only way I can see the starting style rules is for element that are added while the inspector is already open. > So for my test page, it's visible on divs that are added with the "Add div" button. > > Would you know what's happening? I will check this soon. (Keep my ni until I found the root cause.) Thanks.
(In reply to Nicolas Chevobbe [:nchevobbe][PTO - back on Monday May 13th] from comment #7) > If possible, it would be nice to not return it. For now, I'm filtering the result to only include rules whose parent rule is a `CSSStartingStyleRule` It seems we don't have extra information in the rule node to know if this style rule is in `@starting-style`. I may miss something or need to dig deeper. I could check this later. > Right. I wonder if that could be weird for developers because they won't see the starting-style rules until the transition is triggered, but we might follow up on this Thanks. Resolving it earlier and keeping this value longer need to tweak the framework. We might have to change a lot, but yes, we could follow up on this. > I updated https://phabricator.services.mozilla.com/D209329 and I can see starting style rules in some cases. > It seems that there's something odd with `InspectorUtils.getCSSStartingStyleRules` for transitions triggered before the inspector is opened/registered? > I have this test page https://ffx-devtools-starting-style.glitch.me/ , where I have a few @starting-style applying to the body, the h1 and div > If I inspect the body or the h1, I'm not getting the starting style (which is properly applies, the transition is visible on screen) > The only way I can see the starting style rules is for element that are added while the inspector is already open. > So for my test page, it's visible on divs that are added with the "Add div" button. > > Would you know what's happening? I will check this soon. (Keep my ni until I find the root cause.) Thanks.