Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8459323
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 10, 20262026-06-10T13:18:07+00:00 2026-06-10T13:18:07+00:00

I use Chrome Developer Tools to debug my JavaScript code, but I have one

  • 0

I use Chrome Developer Tools to debug my JavaScript code, but I have one pet peeve with the way Chrome lets you edit the JavaScript files under the Scripts tab. Sometimes, I do not realize that I am in Chrome and I start making changes to the code under the Scripts tab, only to realize when I refresh that the changes I had just made were never saved to disk!

I was wondering if there is way to make the code shown in the Scripts tab read-only, so that if I try to edit the file in Chrome, I’ll see that it’s not editable and then realize that I’m not in my IDE.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-10T13:18:08+00:00Added an answer on June 10, 2026 at 1:18 pm

    Use the following process to make the script source read-only in Chrome 32+:

    • Go to the chrome://flags/#enable-devtools-experiments URL

    • Select Allow UI Themes

    • Open Chrome Dev Tools

    • Select Settings (Press F1 or click on the three dots on the far right)

    • Select Allow UI Themes

    • Create a DevTools theme with the following style:

      .content-view.script > .text-editor { -webkit-user-modify: read-only !important; }
      
    • Publish it the the Chrome Web Store

    • Install the Theme

    • Restart Chrome

    References

    • Custom.css has stopped working in 32.0.1700.76 m Google Chrome update
    • Sample DevTools Theme Extension
    • Chrome Developer Edition Dark Theme for Chrome Dev Tools
    • WebCore Inspector Script Content View
    • Chromium User Data Directory

    Use the old process for Chrome 31-:

    Use a user stylesheet to disable the script tab altogether:

    .toolbar-item.scripts { display:none !important; } /* Hide Scripts Tab */
    

    Or simply make the script source read-only:

    .text-editor-editable { -webkit-user-modify: read-only !important; } /* Old selector */
    .content-view.script > .text-editor { -webkit-user-modify: read-only !important; } /* Older selector */
    .editing { -webkit-user-modify: read-only !important; } /* Generic Selector */
    

    Here are several possible locations of the file:

    • Windows 7 Chromium:
      • %LOCALAPPDATA%\Chromium\User Data\Profile 1\User StyleSheets\Custom.css
    • Windows 7 Chrome:
      • %LOCALAPPDATA%\Google\Chrome\User Data\Default\User StyleSheets\Custom.css
    • OSX Chrome:
      • /Users/YourUsername/Library/Application Support/Google/Chrome/Default/User StyleSheets/Custom.css
    • Ubuntu Chrome:
      • ~/.config/chromium/Default/User\ StyleSheets/Custom.css

    Use the following Chrome Devtools URL to reference the relevant styles:

    chrome-devtools://devtools/devTools.css

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I use Google Chrome and its webkit developer tools to write/debug my JavaScript. I
I have tools like firebug and web developer to debug the code with firefox
I would like to debug my javascript application using Google Chrome 3 's developer
I am trying to follow the guide here: https://developers.google.com/chrome-developer-tools/docs/scripts-breakpoints But it doesn't seem to
Whenever I use Console in Chrome's Developer Tools or Firebug to interpret a jQuery
For unknown reasons, when I use Google chrome (version 9.0.597.84), the developer tools aren't
Chrome's developer tools are an excellent set of tools that I love to use.
I use the Google Chrome developer tools. When I want to inspect an element,
The Safari & Chrome developer tools (webkit inspector) seem to have become quite advanced.
I would like to use Google Chrome instead of the WebKit Framework in one

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.