Status Update
Comments
mi...@gmail.com <mi...@gmail.com> #2
jo...@diamond.ac.uk <jo...@diamond.ac.uk> #3
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
th...@yahoo.com <th...@yahoo.com> #4
th...@yahoo.com <th...@yahoo.com> #5
For more details visit
gi...@appspot.gserviceaccount.com <gi...@appspot.gserviceaccount.com> #6
[Monorail components: -Blink>CSS Platform>DevTools>Authoring]
th...@yahoo.com <th...@yahoo.com> #7
Thanks.!
mi...@amarulasolutions.com <mi...@amarulasolutions.com> #8
th...@yahoo.com <th...@yahoo.com> #9
mi...@amarulasolutions.com <mi...@amarulasolutions.com> #10
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visit
th...@yahoo.com <th...@yahoo.com> #11
mi...@amarulasolutions.com <mi...@amarulasolutions.com> #12
wa...@gmail.com <wa...@gmail.com> #13
[Monorail components added to Component Tags custom field.]
wa...@gmail.com <wa...@gmail.com> #14
wa...@gmail.com <wa...@gmail.com> #15
wa...@gmail.com <wa...@gmail.com> #16
mi...@amarulasolutions.com <mi...@amarulasolutions.com> #18
is...@google.com <is...@google.com> #19
th...@yahoo.com <th...@yahoo.com>
or...@gmail.com <or...@gmail.com> #20
Why was it closed? This still happens with 3.8, 3.9 and master. See also
nl...@gmail.com <nl...@gmail.com> #21
nl...@gmail.com <nl...@gmail.com> #22
ka...@google.com <ka...@google.com> #23
This is not a bug.
For the dashboard we refresh, but for other search results pages it is just not clear what the better choice is: Reload every time or keep the results fixed. The advantage of "fixed" being that it is quicker and supports better the workflow of checking lots of changes from the results page by going back and forth.
Since both ways can have their pluses and minuses, this realistically not going to change, without a very strong argument.
th...@gmail.com <th...@gmail.com> #24
pe...@olssononline.se <pe...@olssononline.se> #25
I understand that there are pros and cons with both options. However, I would at least expect a configuration option for the users that are used to getting a refreshed UI all the time when jumping around. For our use, this new way of working with manual refreshes all the time would not be accepted within the team at all. At least provide some workaround to make the UI behave as we're used to.
vq...@gmail.com <vq...@gmail.com> #26
My team has been hit by this as well, and I agree with you: providing a configuration option would be a great way to accommodate users who prefer the previous behavior of automatically refreshing the UI. The current approach significantly disrupts our established workflows, and an alternative solution would be greatly appreciated.
Description
Affected Version 3.7.2:
Gerrit 3.5 used to refresh the dashboard automatically as changes came in. When we updated to 3.7.2 the dashboard no longer refreshes automatically and we have to refresh the page manually.
Is there a setting that allows the dashboard to automatically refresh in 3.7.2 much like the old behavior?
What is the expected output?
Refresh UI if we submit a patch, abandon etc.
What do you see instead?
We need to use CTRL+R
What is the output of the JS console log (if applicable)?
What is the performance record (seehttps://developers.google.com/web/tools
/chrome-devtools/evaluate-performance/reference#record)(if applicable)?
Please provide any additional information below.