Front-End FAQs and Causes (i)

JS section:

1. Refer to the Public template page (the template generally refers to its corresponding JS file) to a page, some functions are not available and the console does not error.

Check the wrong way: see other references to the template page features are available, if other pages available, compare the current page and template page reference to the JS file is not a conflict, if the other page this feature is still unavailable, see if the function is wrong.

(Refer to JS conflict, common is the conflict caused by multiple jquery libraries)

2. On the same page, the same way trigger and generate the prompt box, some can trigger and display normally, and some only when the page is triggered and display, the console does not error.

Check the wrong way: see if the ID used to generate the box is the same, if the same, then changed to a different ID, if different, the use of Firedebug breakpoint debugging error.

CSS section (using the bootstrap template):

1. Change a property of a selector, such as a color property, the page color is still unchanged.

Error-checking: View the relevant definition of its style in the browser tool.

Causes are: First, the original definition used '! Important '; the definition of the current color is not in the corresponding style table but in the <style> tag of the header of the current page.

2. Changing the class parent container name only changes its Position property, the font color of the sub-container changes when the class sub-container does not change.

Error-checking: View the relevant definition of its style in the browser tool. Cause: The definition of a class sub-container is restricted by the original class parent container, and the font color of the original class child container changes when the class parent container changes. How to modify: The class parent container is unchanged, and the ID selector is added to the tag where it is located, and the attribute to be modified is defined.

Front-End FAQs and Causes (i)