In the daily development of mobile terminal, we usually try the mobile terminal mode of Chrome browser for development and debugging. Only when chrome debugging is completed, can we go to the real machine for testing if there is no problem. This is the big problem of mobile terminal development,
Various brands and models of mobile phones, various types of browser apps in mobile phones....... Fortunately, the mobile terminal is relatively consistent, but there are always some kinds of pits, which makes it painful. It is clear that chrome debugging tools are normal,
Once in a browser, it will explode. What can I do? I can't use the debugging tools in chrome for debugging. I can only use the alert() pop-up window for debugging. What can I do to debug as clearly and visually as on a PC?
Today, I found a cool mobile debugging tool for fried chicken eruda , a little bit of history;
Eruda is a debugging panel specially designed for the front end of mobile web pages, similar to the mini version of devitools. Its main functions include: capturing console logs, checking element status, displaying performance indicators, capturing XHR requests, displaying local storage and Cookie information, browser feature testing, etc.