- Chrome
- "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"
Issues:
- "Back" or "Reload" jumps around on page.
- Click on TXT file downloads instead of displays in browser
- No "Edit page" option.
|
How to
- How to delete cookies for one site:
- Settings - Privacy - Third party cookies - See all site data (can sort and search) - Trash icon to clear
- To print with background color (e.g. color cell of a table):
Print - More settings - Background graphics
- To turn Bookmarks bar on and off:
- To always see full URL:
- Right-click in URL line - "Always show full URL"
- To enable/disable plugins:
chrome://plugins
Maybe obsolete
- Cookie Deprecation messages in console
- Embed YouTube video gives warnings that fill the console.
- Can make it hard to debug rest of page.
- To turn these warnings off:
chrome://flags - Cookie Deprecation messages - disable
- 2018 update makes Chrome blurry
- TD VALIGN has odd behaviour in Chrome.
- Solution: Avoid using it.
- Chrome bug - rotated images
- Solution: Find and fix images.
- Chrome extension to rotate images in the browser:
- Image zoom not working.
- Solution: Ctrl + mouse wheel to re-size.
- Other solution: Settings - Advanced - Web content - Page zoom - needs to be 100.
- If Favicons get corrupted. Solution:
- Close Chrome.
- Delete this file:
User Data\Favicons
- Re-start Chrome.
- Chrome PDF viewer won't save PDF file to disk
- Solution -
about:plugins
- disable it
Task Manager
- Menu - More Tools - (Chrome) Task Manager
- or Right-click top of browser window - Task manager
- If can't close tab/page without a dialog:
- Task Manager - kill tab or page
- Task Manager can show how much memory tabs and plug-ins are using.
- JavaScript Console (Ctrl-Shift-J)
- Right-click - Inspect element
- Might need ">>" for further menus
Stop caching while developing:
- [3 dots] - Settings - Network - "Disable cache (while DevTools is open)"
How to do things:
- To wrap long lines so can see full element:
Settings icon - "Elements" - Word wrap
That means it only works in "Elements" section.
Apparently cannot get word wrap in "Console" section!
- To view HTTP headers:
Network - (Reload page) - (select a request) - Headers
- To view cookies:
Application - Cookies
- To view entire current page (after JS transforms) as HTML:
Elements - body - right-click - Edit as HTML
- To see all JS and other files included:
- Network - JS (or Sort by type)
- To inspect images on page:
- Application - Frames - top - Images
- To convert image to
Data URI
- Chrome console - Top menu >> Application
- Bottom panel - Frames - top - Images
- Right-click image and "Copy image as data URI"
- No option for converting audio to Data URI though.
Capturing all network calls
A tricky problem:
- "Network" captures network calls in a tab.
- If the link opens in a new tab, though, "Network" will not be on in that tab to capture it.
By the time you turn it on, you may have missed some network calls.
To see what network calls were made in opening the new tab,
a solution is
here.
- Force open links in same tab. See JS code to paste in console.
- "Network" - Tick "Preserve log" so log is not cleared.
Live edit
- Can edit local copy of page with JS.
For example to replace the n'th image, open Console and type:
x = document.getElementsByTagName('img')
x[n].src = "new url"
- Live edit CSS:
- Inspect element
- Styles
- Tick boxes on and off
- Edit values
- To edit cookies:
EditThisCookie
Chrome extensions causing console error
- Here was a very difficult bug to track down.
- I was getting console errors:
Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true,
but the message channel closed before a response was received
- I was only checking this on the site I use the console for.
I assumed something was wrong with that site.
A lot of time was wasted debugging that site.
- I made two wrong assumptions:
- I assumed the site I use the console for had the problem.
I should have checked the console on all sites.
It turns out it was happening on all sites.
- I assumed a site itself generates its own console errors.
It did not occur to me there could be something wrong with the browser.
- Eventually I found the
answer.
It was caused by the Adobe PDF extension
to Chrome.
- Solution: Disable Adobe PDF extension.
- In fact,
many Chrome extensions may cause this error.
Ancient Brain