WAI
Status Update
Comments
an...@gmail.com <an...@gmail.com> #2
[Empty comment from Monorail migration]
[Monorail components: -Platform>DevTools Blink>CSS]
[Monorail components: -Platform>DevTools Blink>CSS]
rh...@google.com <rh...@google.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
an...@gmail.com <an...@gmail.com> #4
Hi, no disrespect, but please forward this to developer who knows CSS and HTML. I have explained the issue perfectly.
rh...@google.com <rh...@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
rd...@google.com <rd...@google.com> #6
[Empty comment from Monorail migration]
[Monorail components: -Blink>CSS Platform>DevTools>Authoring]
[Monorail components: -Blink>CSS Platform>DevTools>Authoring]
an...@gmail.com <an...@gmail.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.!
rd...@google.com <rd...@google.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.
an...@gmail.com <an...@gmail.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.
rd...@google.com <rd...@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
an...@gmail.com <an...@gmail.com> #11
[Empty comment from Monorail migration]
rd...@google.com <rd...@google.com> #12
[Empty comment from Monorail migration]
an...@gmail.com <an...@gmail.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.]
ad...@google.com <ad...@google.com> #14
This is working as intended. Please see -
Any discrepancies between time series detail-level totals vs daily summary totals is likely due to how the device calculates on-wrist and off-wrist data. On-wrist data is defined as data collected while the device is worn. On-wrist data is also referred to as Intraday data. Off-wrist data is defined as data collected while the device is not worn. For example, step data can be collected if the device was in a bag while driving down a bumpy road. By design, daily summary totals include on-wrist totals and off-wrist totals; while Intraday totals include on-wrist totals only.
Description
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of issue is this? Other issue
When did this happen?
Nov 23, 2022 11:40 PM GMT+01:00
What steps would let us observe this issue?
1. I have for example 20600 steps within Fitbit App. Steps will be synced with health connect to Google fit. In Google Fit only approx. 15000 steps are shown.
2. This is everyday. Health connect syncs all information of from Fitbit to Google Fit and in Google Fit there are always less steps.
What did you expect to happen?
Exact same value of Fitbit steps in Google Fit synced by Health connect
What actually happened?
There are always differences within the step values of thousand of steps.
How often has this happened?
Every time
What was the effect of this issue on your device usage, such as lost time or work?
Moderate
Related apps
Health Connect
com.google.android.apps.healthdata
Version 35425 (0.1.1289.488642842.5-open_beta)
Not system app
Debugging information
Google Play-Dienste
com.google.android.gms
Version 224515044 (22.45.15 (190400-488417729))
System App (Updated)
Android System WebView
com.google.android.webview
Version 530410534 (107.0.5304.105)
System App (Updated)
Network operator: HoT
SIM operator: HoT
Filed by Android Beta Feedback. Version (Updated): 2.30-betterbug.external_20221026_RC02
To learn more about our feedback process, please visit