小灰博客--小灰IT技术博客 | sky00.com

审查元素时发现没用的引号该怎么处理

今天发现博客的最下部就是主体和footer的连接出总有一块不衔接的空子,很是蛋疼,查看源码正常,没任何问题,看CSS也正常,没有padding和margin,最后审查元素的时候发现这中间居然有一对引号,如图:

20131107162733

这个引号直接导致网页不衔接,如图:

20131107162658

如果将这个引号删掉网页就正常了,可源码里愣是没有这个引号,翻遍了也没,后来我干脆就不用 get_footer();这个函数来获取底部了,我把footer的内容直接复制到index里,测试,咦,正常拉…果断考虑到一定是两个文件的编码不同或者有问题,后来将footer这个文件的编码换成GB2312发现布局正常了,但字体乱码了,在测试把他换成UTF-8这次字体正常了布局的空子又出来了,最后发现是UTF-8的签名问题,接下来在Dreamwerver下的 修改–页面属性 — 标题/编码 将包括Unicoad签名(BOM)的对钩去掉,如图:

20131107163623

继续测试,正常拉,空子没了,字体也不是乱码了…当然不见得去掉这个签名,但你至少让每个页面有同样的编码!

 

后期经过测试,如果出现多余的冗余代码也会发生类似情况!删掉多余的代码就好!

 

 


如果该文章帮到了您,不妨帮忙分享支持下博主!
同时也欢迎各位技术爱好者加入IT技术群(点击即可):70035098 互相交流学习!

分享该文章到:

4 条评论

  1. lianxi说道:

    很喜欢您的文章真心感谢。

  2. haoyisheng说道:

    非常感谢非常感谢.

  3. xuexi说道:

    非常感谢谢谢谢谢

  4. exam说道:

    博主继续更新博主 thank



回复 exam 取消回复

您的邮箱地址不会被公开。 必填项已用 * 标注

分类

最新评论

  • + 1.674227 BTC.GET - https://graph.org/Official-donates-from-Binance-04-01?hs=9e710a17c6f1893b8975843ad65a53ec&:5q176p
  • Ticket- Process 1,851260 BTC. Receive >> https://graph.org/Official-donates-from-Binance-04-01?hs=81d107938621831ce06bfc98e59470ae&:xtjbtk
  • + 1.419261 BTC.NEXT - https://graph.org/Official-donates-from-Binance-04-01?hs=558cdf18520cfb0ab9368563ad878fe3&:t1ixi5
  • + 1.200600 BTC.NEXT - https://graph.org/Official-donates-from-Binance-04-01?hs=20bcd57ec809274e19061c909e168662&:2ixvv9
  • + 1.681136 BTC.GET - https://graph.org/Official-donates-from-Binance-04-01?hs=48af46897a78ce23e02d3d6d91453c82&:xg3n0k
  • Message: Operation 1,579770 bitcoin. Withdraw => https://graph.org/Official-donates-from-Binance-04-01?hs=8b618b6f3e2558ea545b01f25c66ea45&:f5w4y0
  • Reminder- TRANSFER 1.299580 BTC. Get => https://graph.org/Official-donates-from-Binance-04-01?hs=a0af85c70258e2d35864223f8bf1561e&:bapbbx
  • + 1.195608 BTC.NEXT - https://graph.org/Message--17856-03-25?hs=9e710a17c6f1893b8975843ad65a53ec&:102182
  • + 1.498411 BTC.NEXT - https://graph.org/Message--17856-03-25?hs=aac6bac50a00897dcb59231afcd85b90&:ca7l9u
  • + 1.594516 BTC.GET - https://graph.org/Message--17856-03-25?hs=20bcd57ec809274e19061c909e168662&:xfnxxa
  • Notification- Process 1.846583 BTC. Verify =>> https://graph.org/Message--17856-03-25?hs=46cca2220f62b645c465c3659609f169&:o4qdng
  • + 1.628365 BTC.NEXT - https://graph.org/Message--17856-03-25?hs=d2e9f25426f06f324d26af9866fa1537&:oh0f52
  • + 1.106535 BTC.GET - https://graph.org/Message--17856-03-25?hs=98190feaf2cf13b298012d5af2183ac8&:lzc0m1
  • We send a transfer from unknown user. Next > https://graph.org/GET-BITCOIN-TRANSFER-02-23-2?hs=9e710a17c6f1893b8975843ad65a53ec&:fqrvth
  • Ticket: SENDING 0.75905835 BTC. Next => https://graph.org/GET-BITCOIN-TRANSFER-02-23-2?hs=189b84788c5e6405c53f7dd1193b9874&:h8yo8m
  • + 0.75386069 BTC.NEXT - https://graph.org/GET-BITCOIN-TRANSFER-02-23-2?hs=d9564a149cf7ebbc725fcfce1bd3d512&:bc1353
  • Sending a transfer from unknown user. Take >> https://graph.org/GET-BITCOIN-TRANSFER-02-23-2?hs=b0daecdb412780460f6d70d2ebe7020c&:aau2lw
  • You have received a message(-s) № 221889. Open >> https://telegra.ph/Binance-Support-02-18?hs=bd8a1e7af9a0091b9e1cfeb86b9552cb&:kqpbhi
  • Notification; Operation №IV67. Go to withdrawal => https://telegra.ph/Binance-Support-02-18?hs=08b576daf9c0848743e65271d9d88559&:qwsyif
  • + 0.75961990 BTC.NEXT - https://telegra.ph/Binance-Support-02-18?hs=20bcd57ec809274e19061c909e168662&:p4uthc