Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Developer Tools settings not persisting after closed #20491

Closed
JoaoHamerski opened this issue Jan 13, 2022 · 16 comments · Fixed by brave/brave-core#12600
Closed

Developer Tools settings not persisting after closed #20491

JoaoHamerski opened this issue Jan 13, 2022 · 16 comments · Fixed by brave/brave-core#12600
Assignees

Comments

@JoaoHamerski
Copy link

JoaoHamerski commented Jan 13, 2022

Description

The settings for developer panel (F12) just doesn't persist, any checkbox or option i try to change is reseted after i restart the browser, already tried to reinstall the browser, i even reinstalled the OS

Steps to Reproduce

  1. Press F12 to open developer panel
  2. Press F1 to open settings
  3. Check any checkbox or uncheck it, for example, "Log XMLHttpRequests"
  4. Restart the browser or just close the dev-tools.

Actual result:

The option will be reseted to default.

Expected result:

The option setted should persist.

Reproduces how often:

Easily reproduced

Brave version (brave://version info)

Brave | 1.34.80 Chromium: 97.0.4692.71 (Official version) 64 bits
Revision | adefa7837d02a07a604c1e6eff0b3a09422ab88d-refs/branch-heads/4692@{#1247}
SO | Linux

Version/Channel Information:

  • Can you reproduce this issue with the current release?
    Yes

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields?
    No

  • Does the issue resolve itself when disabling Brave Rewards?
    No

  • Is the issue reproducible on the latest version of Chrome?
    No, on Chrome it's working as intended.

@JoaoHamerski
Copy link
Author

So am i the only one having this annoying issue? I'm using Chrome until this get fixed, i need "Log XMLHttpRequest" settings on to web development but every time it gets disabled.

@hugonasciutti
Copy link

hugonasciutti commented Jan 18, 2022

So am i the only one having this annoying issue? I'm using Chrome until this get fixed, i need "Log XMLHttpRequest" settings on to web development but every time it gets disabled.

I am having the same problem as well, any configuration is lost when dev-tools is closed and reopen, I don't even need to restart the browser for it to happen.

I noticed this when I added a new Custom Device for testing, and lost every time I reopen dev-tools.

Brave version (brave://version info)

Brave 1.34.80 Chromium: 97.0.4692.71 (Official Build) (64-bit)
Revision adefa7837d02a07a604c1e6eff0b3a09422ab88d-refs/branch-heads/4692@{#1247}
OS Linux

@JoaoHamerski JoaoHamerski changed the title Brave developer settings not persisting after reboot Brave DevTools settings not persisting after closed Jan 21, 2022
@JoaoHamerski
Copy link
Author

JoaoHamerski commented Jan 21, 2022

@hugonasciutti I just tested and can confirm now, this bug happens when dev-tools is closed to me as well, i just updated the issue title to a more accurated one.

@cyress
Copy link

cyress commented Jan 24, 2022

Related tickets: #20075, #19530, #19509, #19871

@JoaoHamerski
Copy link
Author

Still not fixed on Brave "stable" 1.35.100

@twopills
Copy link

twopills commented Feb 3, 2022

Still not fixed on Brave "stable" 1.35.100

I tried version 1.35 now, to me it seems to work.

@JoaoHamerski
Copy link
Author

@twopills It's really still bugged to me.

I just open devtools > settings > enable LogXMLHTTPRequest > close devtools > open it again > LogXMLHTTPRequest is disabled.

Also the changelog not mentioned anything about it.

@LeonFedotov
Copy link

very annoying, back to chrome >:(

@Lemonawa
Copy link

I also have the same problem.Fuck that nobody replied me 👎

@KnifeFed
Copy link

Why isn't anybody from the Brave team even acknowledging this issue, anywhere?

@twopills
Copy link

twopills commented Feb 24, 2022

@twopills It's really still bugged to me.

I just open devtools > settings > enable LogXMLHTTPRequest > close devtools > open it again > LogXMLHTTPRequest is disabled.

Also the changelog not mentioned anything about it.

Hey @JoaoHamerski now i tried and i have the bug . Sh*t

@Lemonawa
Copy link

I back to chrome. 👎

@hugonasciutti
Copy link

hugonasciutti commented Feb 24, 2022

Hey @rebron or @JoaoHamerski, could you add the bug label for this issue get a higher priority?

@rebron rebron added the needs-investigation A bug not 100% confirmed/fixed label Mar 1, 2022
@rebron rebron added the priority/P4 Planned work. We expect to get to it "soon". label Mar 8, 2022
@goodov goodov self-assigned this Mar 15, 2022
@rebron rebron added priority/P3 The next thing for us to work on. It'll ride the trains. and removed needs-investigation A bug not 100% confirmed/fixed priority/P4 Planned work. We expect to get to it "soon". labels Mar 15, 2022
@bsclifton
Copy link
Member

Quick update for anyone subscribed - this is fixed in our latest Nightly and will be making it to Beta and Release versions soon

@kjozwiak
Copy link
Member

Above will require 1.37.101 or newer for 1.37.x verification.

@GeetaSarvadnya
Copy link

GeetaSarvadnya commented Mar 28, 2022

Verification PASSED on


Brave | 1.37.106 Chromium: 100.0.4896.46 (Official Build) (64-bit)
-- | --
Revision | 5ca33821b2211805855c77d334353d27c616a7ca-refs/branch-heads/4896@{#584}
OS | Windows 10 Version 21H2 (Build 19044.1586)

Went through the STR/Cases outlined via #20491 (comment) and also ensured the following:

  • ensured that changes to Preferences are preserved when the browser has been restarted
  • ensured that changes to Experiments are preserved when the browser has been restarted
  • ensured that new devices that are selected via Devices are preserved when the browser has been restarted
  • ensured that custom locations are preserved under Locations when the browser has been restarted

@rebron rebron changed the title Brave DevTools settings not persisting after closed Developer Tools settings not persisting after closed Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.