2018 latest front-end interview questions twelve-JS Tutorial-php.cn

2018 latest front-end interview questions twelve

php中世界最好的语言

Release： 2020-09-01 15:46:41

Original

3285 people have browsed it

This time we bring you the latest front-end interview questions in 2018. We know that interviews are an essential part of front-end work. This time, the common front-end interview questions are sorted and summarized to help you get through the front-end interview. Big trouble. Let’s take a look.

[Related recommendations: Front-end interview questions (2020)]

1. What is your favorite picture replacement method? How you choose to use it.

Designers can replace the original text in an element with a background image to display a more beautiful font. Implementation method 1: Add span tag The implementation of this technique is very simple: surround the text in the element with a span, then hide the text in this span by applying CSS styles, and finally apply the background image to the element. For example, take the following HTMl tag. 2. Negative text-indent propertyvalue Designer Mike Rundle proposed a method of using negative text-indent property values to push the text beyond the left edge of the screen. Although the applicability of this solution is not widespread - IE 5.0 will push the background image out of the viewer's line of sight along with the text - it is quite simple and elegant. Disadvantages: Does not solve the accessibility problem of blank pages after the browser disables images; sometimes does not work in IE 5.0.
Significance: The image replacement technology retains the original text in the replaced element, so understanding the page content is not a problem for any customer. Mainly consider SEO, not visual effects.

2. How would you solve the style problem of a specific browser?

The so-called browser compatibility problem refers to the situation where different browsers have different parsing of the same piece of code, resulting in inconsistent page display effects. In most cases, our requirement is that no matter what browser the user uses to view our website or log in to our system, there should be a unified display effect. Therefore, browser compatibility issues are issues that front-end developers often encounter and must solve.

Before learning about browser compatibility, I would like to divide front-end developers into two categories:

The first category is front-end developers who develop according to the design drawings accurately, which can be said to be accurate. 1px, they can easily find the shortcomings of the design drawing, and in rare cases they will encounter browser compatibility issues, and these problems are often caused by browser bugs, and the pages they create are easy to maintain later. , there are few code reuse issues, and it can be said to be a relatively stable and reliable code.

The second category is front-end developers who basically develop according to the design drawings. Many details are very different, such as spacing, line height, picture position, etc., which often differ by a few px. The realization of a certain effect is obtained through repeated debugging. The specific reason why this effect occurs is still vague, and the overall layout is very fragile. The slightest change makes it a mess. I don’t know why the code is written this way. Such developers often struggle with compatibility issues. After modifying this browser, it messed up another browser. I changed it over and over but still had no clue. In fact, most of the compatibility issues they encountered should not be blamed on the browser, but on their technology itself.

This article is mainly aimed at the first category, rigorous developers, so here we mainly analyze compatibility issues from the perspective of browser parsing differences. (Recommended related articles: Mainstream browser CSS 3 and HTML 5 compatibility list)

I believe you have mastered the method after reading the case in this article. For more exciting information, please pay attention to other related articles on the php Chinese website!