sharepoint 2010 页面刷新时滚动条位置保持不变 Controlling scrollbar position on postback

本文介绍了一种在SharePoint2010中实现滚动条位置记忆的方法,即使在页面刷新后也能保留用户的滚动位置。此技巧通过修改母版页并添加JavaScript代码实现。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

在sharepoint 2010中,如果当前页面的篇幅比较长,如何在拉动页面滚动条时,在刷新的条件下,保持滚动条位置,研究了一下,发现sharepoint 2010的母板页,和普通的asp.net页面有不太一样的地方,是通过一个属性document.getElementById("s4-workspace").scrollTop来控制的,以下是实现的脚本,只需要修改一下v4.master母版页,在里面添加一个javascript的方法。

html {overflow: auto;}/*better than on the body

  body {
     xoverflow:hidden;/*Needed to eliminate scrollbars*/
     background:#000;
     font: normal 80%/1.4  verdana, arial, sans-serif;  
 }
  </style>
  <script>
   window.onload =function()
   { 
       document.getElementById("s4-workspace").scrollTop=1;
       document.body.scroll='yes';
       document.getElementById("s4-workspace").style.overflow='auto';
    }
  </script>

在IE7,IE8,IE9,Google Chrome谷歌浏览器中,测试通过。

### DDR4 Refresh and Precharge Read Address Error Solution In DDR4 memory operations, ensuring correct timing between refresh commands and precharge/read operations is crucial to avoid read address errors. When a row in the DRAM array undergoes a refresh operation while another part of the system attempts to access data from it through a read command, conflicts can arise leading to incorrect addresses being accessed or corrupted data reads. To mitigate these issues effectively: The Memory Controller must implement strict arbitration policies that prevent overlapping critical operations such as refreshing rows with pending read requests targeting those same rows[^1]. This involves careful scheduling where any request involving an active bank undergoing self-refresh should be delayed until completion of its cycle before proceeding further. Additionally, implementing advanced features like Adaptive Refresh Management (ARM), which dynamically adjusts refresh rates based on temperature sensors within DIMMs, helps maintain optimal performance without compromising reliability during high-temperature conditions when retention times decrease significantly requiring faster refresh cycles. For developers working at lower levels interfacing directly with hardware interfaces controlling DDR4 modules, incorporating sufficient delays using NOPs (No Operation instructions) strategically placed around sensitive areas prone to contention points could also serve as preventive measures against potential race conditions causing erroneous behavior due to simultaneous accesses by different parts of systems sharing common resources like buses connecting controllers to physical memories. ```c++ // Example C++ code snippet demonstrating delay implementation void perform_refresh_with_delay() { send_refresh_command(); // Insert appropriate number of No Operations here depending upon specific requirements __builtin___clear_cache((char*)&NOP_instruction_start,(char*)&NOP_instruction_end); } ```
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值