Which is not ture about Smartnavigation ?
-
retain only the last page visited in the browser's history
-
eliminate any flash caused by navigation
-
Doesn't work with sites protected with SSL
-
persist scroll position when moving from page to page
SmartNavigation was an ASP.NET 1.x feature that reduced page flash, persisted scroll position, and maintained focus. However, it had known limitations and did NOT work properly over SSL (HTTPS) connections due to how it handled page navigation. This is a documented limitation of the feature. The other options describe things SmartNavigation DID do (persist scroll position, eliminate flash), so they're incorrect as 'not true' statements. The answer correctly identifies the SSL limitation.
To answer this question, let's go through each option to understand why it is correct or incorrect:
Option A) retain only the last page visited in the browser's history - This option is incorrect. SmartNavigation does not affect the browser's history. It is a technique used to prevent screen flickering during page navigation.
Option B) eliminate any flash caused by navigation - This option is correct. SmartNavigation is designed to eliminate the flickering effect that occurs when a page is being reloaded.
Option C) Doesn't work with sites protected with SSL - This option is incorrect. SmartNavigation does work with sites protected with SSL. It is not dependent on the security protocol being used.
Option D) persist scroll position when moving from page to page - This option is correct. SmartNavigation has the capability to remember the scroll position of a page when navigating to another page.
The correct answer is C. This option is incorrect because SmartNavigation works with sites protected with SSL.