为什么在分页时重绘整个页面？ [英] Why Redraw of the whole page when paginating?
问题描述
您好，请访问网站 http：//www.prismatest。 ch / catalog / EM.ASPX
（user = prismashop，password = minicooper）。通过
列表进行分页时，每次在firefox和IE6上重新构建页面。在大多数
其他网站上，浏览器只是重新绘制了不断变化的区域。
有谁知道为什么会这样？我使用了很多DIV和SPAN并且
远离了不合适的TABLE（除了标题
bar）。我也使用了很多CSS。这是我必须支付的价格
建立一个现代的页面？
感谢您的任何见解
Urs
< blockquote> ur*@prismanet.ch 写道：
请查看网站 http://www.prismatest.ch/catalog/EM.ASPX
（ user = prismashop，password = minicooper）。通过
列表进行分页时，每次在firefox和IE6上重新构建页面。在大多数其他网站上，浏览器只是重绘了不断变化的区域。
有谁知道为什么会这样？我使用了大量的DIV和SPAN，并且远离了不合适的桌子（除了标题
栏）。我也使用了很多CSS。这是我必须支付的价格
建立一个现代的页面？
我认为大多数网站会重绘整个页面 - 他们必须这样做因为要求整个
新页面当您单击其中一个分页箭头时。
的差异可能是在其他网站上的反应是如此之快，以至于你没有注意到它。我不知道为什么这个网站的窗口长时间空白
。
嗨哈伦，谢谢你的回复。
我试着让自己更清楚。看看这个页面：
http://www.citydisc.ch/s/search.cfm?...group_detail=0
这个网站很慢。但是，当您对列表进行分页时，
上一页在最后一刻保持可见，并且立即绘制下一页
页面。
将此与我的网站进行比较：按下>后，该页面几乎立即全部变为白色
按钮。然后它一直保持白色，直到最后一位
被下载。我希望上一页留在屏幕上，
而不是屏幕全白。我希望现在已经足够清楚了。
Urs
ur*@prismanet.ch 写道：请查看网站 http://www.prismatest.ch/catalog/EM.ASPX
（user = prismashop，password = minicooper）。通过
列表进行分页时，每次在firefox和IE6上重新构建页面。在大多数其他网站上，浏览器只是重绘了不断变化的区域。
有谁知道为什么会这样？我使用了大量的DIV和SPAN，并且远离了不合适的桌子（除了标题
栏）。我也使用了很多CSS。这是我必须支付的价格
建立一个现代的页面？
页面是70+ K - 标记和代码，而不仅仅是图像。您可以使用大图像获得
，因为如果它是预先设定的尺寸，页面将在框周围绘制
。但是在这里我们看到大量的大小是
成堆的不需要的javascript和内联样式，以及不需要的嵌套，
和longwinded onckick调用。这一切都使得页面几乎不可读，
也是如此，因此维护将非常耗时。为什么不把你的
语言学习技能用于服务器端解决方案并保持页面
本身非常简单？
Hi, please look at the site http://www.prismatest.ch/catalog/EM.ASPX
(user=prismashop, password=minicooper). When paginating through the
list, the page rebuilds itself every time on firefox and IE6. On most
other sites, the browser just redraws the changing areas.
Does anyone know why this is happing? I used lots of DIVs and SPANs and
stayed away from TABLEs where not appropriate (except for the title
bar). I also use lots of CSS. Is this the price I have to pay for
building a "modern" page?
Thanks for any insight
Urs
ur*@prismanet.ch wrote:Hi, please look at the site http://www.prismatest.ch/catalog/EM.ASPX
(user=prismashop, password=minicooper). When paginating through the
list, the page rebuilds itself every time on firefox and IE6. On most
other sites, the browser just redraws the changing areas.
Does anyone know why this is happing? I used lots of DIVs and SPANs and
stayed away from TABLEs where not appropriate (except for the title
bar). I also use lots of CSS. Is this the price I have to pay for
building a "modern" page?
I think most sites redraw the whole page--they''d have to because a whole
new page is being requested when you click one of the paging arrows. The
difference may be that on other sites the response is so fast that you
don''t notice it. I don''t know why the window remains blank for so long
for this site.
Hi Harlan, thanks for the reply.
I try to make myself more clear. Take a look at this page:
http://www.citydisc.ch/s/search.cfm?...group_detail=0
This site is quite slow. However, when you paginate the list, the
previous page stays visible until the very last moment, and the next
page is drawn immediately.
Compare this to my site: The page becomes all white almost immediately
after pressing the ">" button. Then it stays white until the last bit
has been downloaded. I would like the previous page to stay in screen,
instead of the screen going all white. I hope this is clear enough now.
Urs
ur*@prismanet.ch wrote:Hi, please look at the site http://www.prismatest.ch/catalog/EM.ASPX
(user=prismashop, password=minicooper). When paginating through the
list, the page rebuilds itself every time on firefox and IE6. On most
other sites, the browser just redraws the changing areas.
Does anyone know why this is happing? I used lots of DIVs and SPANs and
stayed away from TABLEs where not appropriate (except for the title
bar). I also use lots of CSS. Is this the price I have to pay for
building a "modern" page?
The page is 70+ K -- of markup and code, not just images. You can get
away with a large image, because if it is pre-sized the page will draw
around the box. But here we see a significant amount of the size is in
piles of unneeded javascript and inline styles, and unneeded nestings,
and longwinded onckick calls. It all makes the page almost unreadable,
too, so the upkeep will be time consuming. Why don''t you devote your
language learning skills to server side solutions and keep the pages
themselves very simple?
这篇关于为什么在分页时重绘整个页面？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
