生活在霸都的一名老程序员，热爱编程，热爱乒乓与篮球，喜欢电影与写作
IP属地：西藏
-
前端面试常见问题——HTML篇
1. HTML语义化 什么是HTML语义化 根据内容的结构化（内容语义化），选择合适的标签（代码语义化） 为什么要语义化在没有样式CSS情况下也以一种文档格式显示，容易阅读搜...
-
前端面试常见问题——JS篇1. 闭包 闭包是指有权访问另一个函数作用域中变量的函数，创建闭包的最常见的方式就是在函数内创建函数，通过函数访问函数的局部变量,利用闭包可以突破作用链域 特性：函数内再嵌套...
-
When working on a web application that involves a lot of JavaScript, one of the first things you learn is to stop tying your data to the DOM. It's all too easy to create JavaScript applications that end up as tangled piles of jQuery selectors and callbacks, all trying frantically to keep data in sync between the HTML UI, your JavaScript logic, and the database on your server. For rich client-side applications, a more structured approach is often helpful. With Backbone, you represent your data as Models, which can be created, validated, destroyed, and saved to the server. Whenever a UI action causes an attribute of a model to change, the model triggers a "change" event; all the Views that display the model's state can be notified of the change, so that they are able to respond accordingly, re-rendering themselves with the new information. In a finished Backbone app, you don't have to write the glue code that looks into the DOM to find an element with a specific id, and update the HTML manually — when the model changes, the views simply update themselves. Philosophically, Backbone is an attempt to discover the minimal set of data-structuring (models and collections) and user interface (views and URLs) primitives that are generally useful when building web applications with JavaScript. In an ecosystem where overarching, decides-everything-for-you frameworks are commonplace, and many libraries require your site to be reorganized to suit their look, feel, and default behavior — Backbone should continue to be a tool that gives you the freedom to design the full experience of your web application.
-
前端面试常见问题——Web篇1. web安全及防护 XSS(cross-site scripting)跨站脚本攻击原理：恶意攻击者往Web页面里插入恶意Script代码，当用户浏览该页之时，嵌入其中We...
-
