_content/js: make tab on selection undoable

People often highlight a selection and type tab, hoping to indent it.
Instead, the editor replaces it with a tab. That's fine - some editors work that way.
But the old implementation did not push that edit onto the undo stack,
so that there was no way to get the deleted selection back. Fix that.

Fixes golang/go#41037.

Change-Id: I9f2aa94ac389a3905d07411b0a156dbc66a7ec8a
Reviewed-on: https://go-review.googlesource.com/c/website/+/366535
Trust: Russ Cox <rsc@golang.org>
Run-TryBot: Russ Cox <rsc@golang.org>
TryBot-Result: Go Bot <gobot@golang.org>
Website-Publish: Russ Cox <rsc@golang.org>
Reviewed-by: Jamal Carvalho <jamal@golang.org>
1 file changed
tree: 3925ccb275bdcd7d1634a134091e24034caf1f92
  1. .eslintrc.json
  2. .gitattributes
  3. .prettierrc
  4. .prettierrc.yaml
  5. .stylelintrc.json
  6. AUTHORS
  7. CONTRIBUTING.md
  8. CONTRIBUTORS
  9. LICENSE
  10. PATENTS
  11. README.md
  12. _content/
  13. _later/
  14. cmd/
  15. codereview.cfg
  16. content.go
  17. go-app-deploy.sh
  18. go.mod
  19. go.sum
  20. internal/
  21. tour/
README.md

Go website

Go Reference

This repo holds content and serving programs for the golang.org and go.dev web sites.

Content is in _content/ (go.dev) and tour/ (tour.golang.org). Server code is in cmd/ and internal/.

To run the combined golang.org+go.dev server to preview local content changes, use:

go run ./cmd/golangorg

The supporting programs cmd/admingolangorg and cmd/googlegolangorg are the servers for admin.golang.org and google.golang.org. (They do not use the _content/ directories.)

Each command directory has its own README.md explaining deployment.

JS/CSS Formatting

This repository uses prettier to format JS and CSS files.

See also:

The version of prettier used is 1.18.2.

It is encouraged that all JS and CSS code be run through this before submitting a change. However, it is not a strict requirement enforced by CI.

Deploying

Each time a CL is reviewed and submitted, the blog is automatically deployed to App Engine. If the CL is submitted with a Website-Publish +1 vote, the new deployment automatically becomes https://go.dev/. Otherwise, the new deployment can be found in the App Engine versions list and verified and manually promoted.

If the automatic deployment is not working, or to check on the status of a pending deployment, see the “website-redeploy-go-dev” trigger in the Cloud Build console.

Report Issues / Send Patches

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.

The main issue tracker for the website repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/website:” in the subject line, so it is easy to find.