Assigned
Status Update
Comments
ga...@google.com <ga...@google.com> #2
[Empty comment from Monorail migration]
[Monorail components: -Platform>DevTools Blink>CSS]
[Monorail components: -Platform>DevTools Blink>CSS]
si...@comeen.com <si...@comeen.com> #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
ga...@google.com <ga...@google.com> #4
Hi, no disrespect, but please forward this to developer who knows CSS and HTML. I have explained the issue perfectly.
ga...@google.com <ga...@google.com> #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
si...@comeen.com <si...@comeen.com> #6
[Empty comment from Monorail migration]
[Monorail components: -Blink>CSS Platform>DevTools>Authoring]
[Monorail components: -Blink>CSS Platform>DevTools>Authoring]
ga...@google.com <ga...@google.com> #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.!
si...@comeen.com <si...@comeen.com> #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.
si...@comeen.com <si...@comeen.com> #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.
ga...@google.com <ga...@google.com> #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
si...@comeen.com <si...@comeen.com> #11
[Empty comment from Monorail migration]
Description
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish:
With the new feature that was recently rolled out, users can set a URL as a screen saver for Google Meet Hardware. This is great for digital signage when the room is not in a meetinghttps://workspaceupdates.googleblog.com/2021/12/set-screen-saver-policy-for-google-meet-hardware.html
Our solution DynamicScreen is 100% web so we can use the URL for GMH screen saver, but we need a way to identify displays on our platform in a way that users can make the connection between our digital signage platform and their hardware on the Google admin console
Our ChromeOS application uses the ChromeOS Directory Device ID from chrome.enterprise.deviceAttributes (https://developer.chrome.com/docs/extensions/reference/enterprise_deviceAttributes/#method-getDirectoryDeviceId ), but this is not accessible without a ChromeOS extension or application
How this might work:
Other information (workarounds you have tried, documentation consulted, etc):
We could generate a random "serial" on the web page and store it in local storage but: