Because it's not a storage editor. It's a storage viewer. Devtools are present to help you develop and debug site code; being able to view storage will help writing proper site code. Editing storage values manually won't help, and as such it's a viewer.

Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"If you want to build a better world for yourself, you have to be willing to build one for everybody." -- Coyote Osborne

Moonchild wrote:Editing storage values manually won't help, and as such it's a viewer.

Well, but DevTools is not only for web-page developers, also for power users / hackers / add-on developers.It is needed and helpful when I sometime need hack, and I don't want to use Firebug or other add-ons.

zcyzcy88 wrote:- Try to delete part of cookies to test how server handle it (test server software)- Some web-app use localStorage to save setting, I want copy it to backup, paste it to restore

If you want to play with requests and test server side handling, it might be better to use an application suited for that, e.g. Postman - https://www.getpostman.com/You can always export a request as cURL from Pale Moon, import it in Postman and play as you wish.

zcyzcy88 wrote:And, further according to your logic, DOM Inspector should also not editable. (double standard)

Incorrect. Editing the DOM and CSS is important to be able to see the immediate layout results in the web page. Not so for cookies and storage.

Please stop making every "wontfix" a fight. There are good reasons why certain things are implemented a certain way. If you want to offer enhancements to them is one thing, making demands to cater to your specific workflow is another. See viewtopic.php?f=13&t=5647

Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"If you want to build a better world for yourself, you have to be willing to build one for everybody." -- Coyote Osborne