# Identifying Who is Responsible for Issue on Chrome


## Reason

If your co-worker or client encounters weird behavior on production website in chrome that is misidentified as a bug, do **NOT** try to fix it but to ask more detail for his/her chrome settings first to recognize whether it's a user problem or not.

## Steps

1. Reproduce the issue by steps on chrome with normal mode.
2. Reproduce the issue by steps on different browsers by reproducing steps.
4. Reproduce the issue on chrome with incognito mode.
5. **(IMPORTANT)** Reproduce the issue on chrome with normal mode and without chrome extensions. (Always remember that some extensions are suck to break your website without any sign and notification.)

6. Reproduce the issue on chrome with incognito mode and without chrome extensions.
7. Update chrome version and re-run 1~5.
8. Reinstall chrome and re-run 1~5.
9. Update OS version and re-run 1~5.
10. If all steps fail, start surverying the root cause and fix it.

## Advices

- (Optional) Log info message in logging system such as amazon opensearch if your web application is very complex.
- 
- (Optional) Migrate with sentry to capture exception automatically.
- 
- If the reproducing steps cross multiple pages, remember to check preserve log in network tab.
- 
- Request headers and response headers section in network tab are very helpful for authentication checks. Especially `Cookie` and `Set-Cookie`.
- 
- 
- Application tab is also helpful to trace authentication and storage in time. Be careful on cookie which has `httpOnly` attribute because it can't be accessed by JavaScript so it can't be overwritten in client side.
- 

###### tags: `Work` `Chrome`