Feature Request P3
Status Update
Comments
ph...@chromium.org <ph...@chromium.org> #2
[Empty comment from Monorail migration]
[Monorail components: -Platform>DevTools Blink>CSS]
[Monorail components: -Platform>DevTools Blink>CSS]
va...@chromium.org <va...@chromium.org> #3
Tested the issue on reported chrome version #87.0.4280.00 using Mac 10.13.6 as per the steps in https://crbug.com/chromium/1159587#c0
Steps:
---------
1. Launched chrome and opened devtools
2. Observed that able to add position and top rules.
Attached screen-cast for reference.
@Reporter: Could you please review the attached screen-cast and let us know if we missed anything from our end.
Requesting you to provide a sample URL/file that reproduce the issue, so that it would be really helpful in triaging the issue.
Thanks
Steps:
---------
1. Launched chrome and opened devtools
2. Observed that able to add position and top rules.
Attached screen-cast for reference.
@Reporter: Could you please review the attached screen-cast and let us know if we missed anything from our end.
Requesting you to provide a sample URL/file that reproduce the issue, so that it would be really helpful in triaging the issue.
Thanks
da...@gmail.com <da...@gmail.com> #4
Hi, no disrespect, but please forward this to developer who knows CSS and HTML. I have explained the issue perfectly.
[Deleted User] <[Deleted User]> #5
Thank you for providing more feedback. Adding the requester to the cc list.
For more details visithttps://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
For more details visit
fu...@chromium.org <fu...@chromium.org> #6
[Empty comment from Monorail migration]
[Monorail components: -Blink>CSS Platform>DevTools>Authoring]
[Monorail components: -Blink>CSS Platform>DevTools>Authoring]
al...@chromium.org <al...@chromium.org> #7
As per https://crbug.com/chromium/1159587#c0 , it seems to be a feature request hence marking it 'Untriaged' and requesting someone from Dev to look into it.
Thanks.!
Thanks.!
ma...@chromium.org <ma...@chromium.org> #8
This is something we’ve been thinking about. We do want to make DevTools more helpful w.r.t. “inactive” styles, i.e. declarations that are covered but still don’t have any effect due to other declarations or rules — like `left: 42px` on a statically positioned element.
ma...@chromium.org <ma...@chromium.org> #9
Making this issue about the originally reported behavior, and filing https://bugs.chromium.org/p/chromium/issues/detail?id=1178508 to track further improvements to “inactive” styles.
[Deleted User] <[Deleted User]> #10
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visithttps://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visit
pf...@chromium.org <pf...@chromium.org> #11
[Empty comment from Monorail migration]
ha...@google.com <ha...@google.com> #12
[Empty comment from Monorail migration]
is...@google.com <is...@google.com> #13
This issue was migrated from crbug.com/chromium/1159587?no_tracker_redirect=1
[Monorail components added to Component Tags custom field.]
[Monorail components added to Component Tags custom field.]
Description
Problem
Suppose we have this in CSS:
#menu{
/* position:sticky; top:0; */
display:inline-block;
clear:both;
float:left;
width:100%;
margin:0;
margin-bottom:15px;
}
In Firefox browser inspect tool we can still see these rules present (because, technically, they ARE present in CSS file!), but with strikethrough lines, meaning those rules are not applied. This is cool for experiments, temporary and quick on/off testing and debugging!
Now, in Chrome Dev Tools we cannot do this. Or can we?
Thanks!