Back button to avoid post?

Hi,
When one of my users hits the javascript ("history.back") link on my page, they encounter a page which asks them to refresh (typical IE one)... I'm assuming this is because the form is done via post. Is there a built in back button in jheadstart taht would help avoid this?
thanks,
Jason

Jason,
No, not a real "Back button". But in the 10.1.2.1 release we do generate breadcrumbs (menu path), which allows the user to go back to previous screens by clikcing on a hyperlink, rather than hitting the browser back button.
Steven Davelaar,
JHeadstart Team.

Similar Messages

  • Hello, i have one issue when i hit back button of F Fox than it will show me " Document Expired " alert message.. i need to avoid this alert.

    Hello, i have one issue when i hit back button of F Fox than it will show me " Document Expired " alert message.. i need to avoid this alert.
    because my site is based on ajax so i need same page with my all activity i perform before i go next page when i hit back button..
    Please give me solutions of this problem if possible.
    Thank you

    Are you sending HTTP response headers that instruct Firefox not to cache the pages?
    You can get a "document expired" message if you use the back button to return to a specific page and the web site has instructed Firefox not to cache the page.<br />
    Firefox tries to retrieve the page from the server, possibly by sending POST data.

  • How to avoid focus issue while navigating via Browser Back button

    Hi
    I'm facing some problem in setting focus on Buttons.
    Please refer application: http://apex.oracle.com/pls/otn/f?p=47869:2
    login credentials:
    Workspace: vsanthanam
    user: vijay
    pswd: apex_demo
    In this application, i have 2 pages.
    Page#2 has Submit button
    Page#3 has Cancel button
    Both buttons are HTML based and can be accessed using access Key ALT + s and ALT + c.
    The problem is:
    When i go back to previous page (pgid#2) of the application using IE Browser's Back Button from pgid#3,
    because of onFocus event set in Submit button, control comes back to pgid#3.
    Is there any possible way to set the focus to other items. so that whenever IE brower back button pressed, application would remain in
    page#2.
    Approaches i took:
    If we use onclick, instead of onfocus then again the problem remains since we have to have onfocus = "this.click();" to incorporate Accesskey features.
    Another way is onKeyup event. if we use onKeyup, we can avoid this browser back issue, but vanishes access key features.
    Any pointers on this would be of great help.
    Many Thanks
    --Vijay
    Please NOTE: I intentionally created two buttons in each page. This is required to have HTML buttons with access key features,
    otherwise application gives some flaws in HTML-accesskey.

    Thanks a ton Andy!
    This is what exactly we require, to change the focus to other items when we move away from page.
    application works perfect now.
    Thank you once again for your handy solutions.
    --Vijay                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Re: [iPlanet-JATO] Back Button functionality

    Hi Mike,
    Our test environment does not include proxy server.
    regards,
    syam.
    Please respond to [email protected]
    cc:
    Subject: Re: [iPlanet-JATO] Back Button functionality
    Guys,
    Please clarify something for me, the JATO code is commented as follows
    protected void addResponseHeaders(RequestContext requestContext)
    // These values should make any proxy between the client and
    // server avoid caching, and ensure that pages from one user
    // can never be seen by another user (if they're cached anyway)
    requestContext.getResponse().addHeader("Pragma","no-cache");
    requestContext.getResponse().addHeader
    ("Cache-Control","private");Yet you make no mention of whether your test environment includes a Proxy
    Server, or does your browser
    go directly to the Application Server's web server?
    Can you clarify, please?
    ----- Original Message -----
    From: <syam_reddy@p...>
    Sent: Wednesday, April 25, 2001 2:59 PM
    Subject: [iPlanet-JATO] Back Button functionality
    >
    Hi,
    We observed the following difference in behaviour between JATO pages
    and NetD served pages.
    We have the following scenario. User will login to the
    site. After login he will get a frame set. This frame set has threeframes.
    Top and bottom frames are used for navigation (to switch between various
    sections on the site.) .The middle frame(main frame) shows the actual
    content. When the the frame set gets loaded main frame shows page1. User
    will click on a link on page1. Page 2 will be loaded in main frame. Atthis
    point if the user clicks on back button , with migrated application(JATO
    pages) the following message appears in the main frame.
    In Netscape Communicator 4.61 the following message appears in the main
    frame :
    Data Missing
    This document resulted from a POST operation and has expired fromcache.If
    you wish you can repost the form data to recreate the document by
    presenting the reload button.
    In IE 4.72/5.5 the following message appears in the main frame:
    Warning : Page has Expired
    The page you requested was created using information you submitted in a
    form.This page is no longer available.As a security precaution, Internet
    Explorer does not automatically resubmit your information for you. To
    resubmit your information and view the web page click teh refresh button.
    However, in the NetD site page1 will appear in main frame.
    How do we mimic the NetD behaviour with the migrated
    applications ?
    We think the above behaviour with migrated Apps, is due to the
    headers that are get set in Application ServletBase , see the following
    code snippet :
    protected void addResponseHeaders(RequestContext requestContext)
    // These values should make any proxy between the client and
    // server avoid caching, and ensure that pages from one user
    // can never be seen by another user (if they're cached anyway)
    requestContext.getResponse().addHeader("Pragma","no-cache");
    requestContext.getResponse().addHeader
    ("Cache-Control","private");
    If we comment the above code , we were able to mimic theNetD
    behaviour. Are there any alternatives/thoughts on how to mimic the NetD
    behaviour ?
    Thanks in Advance,
    syam&ravi.
    [email protected]
    [email protected]

    OK, here's what I'm trying to do: We have, like you said, a menu
    page. The pages that it goes to and the number of links are all
    variable and read from the database. In NetD we were able to create
    URLs in the form
    pgXYZ?SPIDERSESSION=abcd
    so this is what I'm trying to replicate here. So the URL that works
    is
    pgContactUs?GXHC_GX_jst=fc7b7e61662d6164&GXHC_gx_session_id_=cc9c6dfa5
    601afa7
    which I interpreted to be the equivalent of the old Netd way. Our
    javascript also loads other frames of the page in the same manner.
    And I believe the URL-rewritten frame sources of a frameset look like
    this too.
    This all worked except for the timeout problem. In theory we could
    rewrite all URLs to go to a handler, but that would be...
    inconvenient.

  • Session state and browser cache - Back button problem

    Hi all,
    I have a problem (and unless I'm missing something I think we all do) with session state and use of the browser's Back button. I really hope I'm just being dumb...
    Background scenario:
    Page P has a sidebar list allowing the user to select what content is displayed (e.g. 'stuff relating to X, Y or Z' where X, Y and Z are rows in, say, a table of projects). When a list entry is clicked, we branch to page P with the value of the list item placed in an application-level item (call it G_PROJECT). Reports on page P use G_PROJECT in their WHERE clauses.
    So, click list entry X and G_PROJECT is set to X and page P shows reports for project X.
    Page P also has a set of buttons which branch to various edit pages which allow attributes of page P's current project to be updated. These pages similarly use G_PROJECT in their WHERE clauses.
    Problem scenario:
    1. The user goes to page P and picks project X off the list. Project X's stuff is displayed (G_PROJECT = X).
    2. The user then picks project Y off the list. Project Y's stuff is displayed (G_PROJECT = Y).
    3. The user then clicks the browser's Back button. The page is served from browser cache, so project X's stuff is displayed, but G_PROJECT still = Y.
    4. The user clicks an 'Edit' button; we submit, and branch to an edit page which displays (and will edit) data for project Y because G_PROJECT still = Y.
    This is SERIOUSLY BAD NEWS - apart from being confusing, the user's edit permissions on projects X and Y may differ, and so the user may be able to perform 'illegal' updates.
    I've read what I can on this forum and the rest of the web looking for ways to a) inhibit browsers' 'Back' functions and/or b) prevent pages being cached by the browser, but none of them have worked for me.
    Short of waiting for browser manufacturers to recognise that the web is now full of applications as well as static pages, and enable robust programmatic control of cache behaviour, does anybody know how the problem can be avoided - or at least detected?
    Thanks,
    jd
    Failed attempts to date:
    <meta http-equiv="cache-control" content="no-cache">
    <meta http-equiv="cache-control" content="no-store">
    <meta http-equiv="cache-control" content="private">
    <meta http-equiv="cache-control" content="max-age=0, must-revalidate">
    <meta http-equiv="expires" content="Wed, 09 Aug 2000 01:01:01 GMT">
    <meta http-equiv="pragma" content="no-cache">
    Disallowing duplicate submission (page attribute).
    window.history.go(1);

    Thanks Scott,
    I may be being dumb here but I don't see how that would help...
    P250_PROJECT and G_PROJECT are currently kept in sync by app logic. Whichever is used to drive, if the page is rendered from cache then the app logic is not executed, so the rendered page contents are not those keyed by P250_PROJECT, as illustrated in steps 1-4 of the problem above.
    The user sees X, the session items say Y. The engine doesn't know what the user is seeing.
    when page P is POSTed, its hidden item P250_PROJECT should always be used to derive the application item G_PROJECT. Then whether the page was pulled from cache or rendered anew via a click from the sidebar link, the project ID is determined by the contents of that page.
    As I said above I tried this, with the 'Edit' branch set to:
    Set these items: G_PROJECT
    With these values: &P250_PROJECT.
    but it makes no difference. The project ID is not determined by the rendered page contents - the engine gets the value of P250_PROJECT from session state.
    I can code the 'Edit' pages such that they check permissions and if necessary redirect back to p250 (conditional before-header branch), but that's a clunky cure rather than the prevention I was hoping for.
    Please tell me if my understanding is incorrect.
    jd

  • Back button not removing from the stack?

    Hi,
    I have the following code:
    [[self navigationController]pushViewController:_newsDetailController animated:YES];
    However, It doesn't seem to be removing from the stack when the user hits the back button on the UINavigationBar.
    The reason I believe this, is because when you then select another item in my UITableView, it loads exactly the same details as the first time.
    I have tried [_newsDetailController release]; but it still doesn't make any difference. It just crashes after the third selection.
    This is what I'm doing in my didSelectRowAtIndexPath:
    - (void)tableViewUITableView *)tableView didSelectRowAtIndexPathNSIndexPath *)indexPath {
    [[self appDelegate] setCurrentlySelectedBlogItem:[[[self rssParser]rssItems]objectAtIndex:indexPath.row]];
    [self.appDelegate loadNewsDetails];
    Any help would be greatly appreciated. I've spent ages on this!
    It worked fine until I added a UINavigationController.
    Thanks,
    Nick

    Hi Nick, and welcome to the Dev Forum,
    nrawlins wrote:
    ... It doesn't seem to be removing from the stack when the user hits the back button on the UINavigationBar.
    I understand how your observations could make it seem like your _newsDetailController is somehow staying on the stack, but that's not what's going on here. If you want to see the stack, just add some logging before and after pushing or popping:
    NSLog(@"stack: %@", self.navigationController.viewControllers);
    I think we'll need to see more of your code to isolate the problem, but what we're looking for is a logic mistake which causes the detail controller to always display the info for the same item, regardless of which item is selected next. Here's a list of questions to guide your search, and/or show you which code we need to look at:
    1) What's in the array returned by [[self rssParser]rssItems] ? It might help to add some logging in tableView:didSelectRowAtIndexPath like this:
    - (void)tableView(UITableView *)tableView didSelectRowAtIndexPath(NSIndexPath *)indexPath {
    NSArray *item = [[[self rssParser]rssItems]objectAtIndex:indexPath.row]];
    NSLog(@"%s: item=%@", _func_, item);
    [[self appDelegate] setCurrentlySelectedBlogItem:item];
    [[self appDelegate] loadNewsDetails];
    2) What does loadNewsDetails do? It looks like it finds the details for the item stored in currentlySelectedBlogItem. Is that right? Some logging in loadNewsDetails might help to make sure the correct details are loaded there. From your description it sounds like you already had this part of the code working right, but it wouldn't hurt to be sure it's still doing what you expect;
    3) How does the data obtained in loadNewsDetails find its way to the details controller? This is the missing link not shown in the code you've posted so far. I think we need to look at:
    3.1) Where and when the details controller is created;
    3.2) Whether the same controller object is intended to persist from item to item, or whether a new instance of the controller is created each time an item is selected. The latter scheme is usually preferred for best memory management;
    3.3) Is the current item and detail data stored in the detailsController or the app delegate? When is it stored, and when is it used?
    For example, suppose the details controller is only created once and persists for the life of the table view. Then suppose loadNewDetails saves the new details in an ivar of the app delegate, and the code to fetch the new details is in viewDidLoad of the controller.
    In the above scenario, viewDidLoad would run after the details controller was created, and if the details of the first selection were loaded by then, the details for the currently selected item would
    be presented as expected. But viewDidLoad will normally only run once, so when the selection was changed, the new details would never be fetched, and the previous details will be displayed again.
    The best way to avoid this and other related scenarios, is to create a new details controller each time a new selection is made from the table view:
    // MyTableViewController.m
    #import "myAppDelegate.h"
    #import "NewsDetailController.h"
    // called by loadNewsDetails as soon as details have been loaded
    - (void)presentDetailController {
    NewsDetailController *viewController = [[NewsDetailController alloc] // vc retainCount is 1
    initWithNibName:@"NewsDetailController" bundle:nil];
    // store new details in the detail controller; e.g.:
    viewController.navigationItem.title = [self appDelegate].currentlySelectedBlogItem;
    viewController.textView = [self appDelegate].currentDetails;
    [self.navigationController pushViewController:viewController // vc retainCount is 2
    animated:YES];
    [release viewController]; // vc retainCount is 1
    By releasing the new controller in the last line, we reduce its retain count to 1. Now the new controller is only retained by the stack, so when the stack is popped, the new controller will be dealloced.
    If none of the above is helpful, please answer all the questions as best you can and post the indicated code, ok?
    - Ray

  • Have to click back button multiple times

    I have seen same problem posted, but no resolution that has worked for me. On some sites, once I click on a link (once), I have to click the back button 2-3 times to get back to the page I was originally on. If I right click on the back button, I see that 2-3 copies of the linked page are in the back button history. This happens a lot on cbsnews.com. If I click on a photo list on that site, it will load 2-3 copies of every single picture that I look at. I have tried running firefox in safe mode, but the same thing happens. If I visit the site using Chrome, it does not happen. This has been happening since version 29.0; I am currently running 31.0 for windows (8.1).

    Hi there. I avoid that issue by clicking the link I want to check and
    selecting '''open new tab / window..''' This way the page I left will
    still be waiting for me.
    Also, right click the back arrow and choose from the menu.

  • How to get the values retained on clicking the back button in jsp page

    Hi All,
    I had two jsp's search and results. In the search page when i enter some values in the text fields, the rsults will be displayed for that search criteria. I had a back button in the results page. When i click on this back button i will get back to my search page. I am using the following code for this back button.
    <INPUT TYPE="button" VALUE='Back' onClick="javascript:history.go(-1)" class="button">
    Now the problem is when i get back to search page using this back button, i am not able to get the values in the search page which i entered, i am getting all blank values. What should i change to get these values back in the search page. Should i maintain any sessions for this?

    You have no control at all over the back button process. To the server, it's indistinguishable from the user simply tying the URL of your search page. So, you need to store this data server side*.
    When your search page is submitted and processed, store the values you received for each of the fields into the user's session. Then, when the search page is generated, check the session for these values, and for any values that are not null, put their values into the html as the default values for the textboxes and controls you are using. This lets you handle the whole matter on the server's side.
    *barring convoluted, unportable, black-magic javascript trickery which you should definitely avoid                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • My back button and refresh button and my yahoo tool bar are dimmed a lot when I open up firefox. So as a result, I cannot use the back button nor my refresh button AND my yahoo toolbar disappears a lot. I have tried to get on your chat session but it is a

    <blockquote>Locked by Moderator as a duplicate/re-post.
    Please continue the discussion in this thread: [/forum/1/688252]
    Thanks - c</blockquote>
    == Issue
    ==
    I have another kind of problem with Firefox
    == Description
    ==
    My back button and refresh button and my yahoo tool bar are dimmed a lot when I open up firefox. So as a result, I cannot use the back button nor my refresh button AND my yahoo toolbar disappears a lot. I have tried to get on your chat session but it is always closed. I need one on one help. Please reply with resolution.
    == This happened
    ==
    Every time Firefox opened
    == two or three months ago
    ==
    == Firefox version
    ==
    3.6.3
    == Operating system
    ==
    Windows XP
    == User Agent
    ==
    Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.3) Gecko/20100401 (BT-canvas) Firefox/3.6.3 GTB7.0 (.NET CLR 3.5.30729)
    == Plugins installed
    ==
    *-npdnu
    *npdnupdater2
    *Coupons, Inc. Coupon Printer DLL
    *Coupons, Inc. Coupon Printer Plugin
    *The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
    *6.0.12.448
    *RealPlayer(tm) LiveConnect-Enabled Plug-In
    *RealJukebox Netscape Plugin
    *Default Plug-in
    *Adobe PDF Plug-In For Firefox and Netscape "9.3.2"
    *BrowserPlus -- Improve your browser! -- http://browserplus.yahoo.com/
    *Shockwave Flash 10.0 r45
    *Yahoo Application State Plugin version 1.0.0.7
    *3.0.50106.0
    *My Web Search Plugin Stub for 32-bit Windows
    *Google Updater pluginhttp://pack.google.com/
    *Google Update
    *Next Generation Java Plug-in 1.6.0_20 for Mozilla browsers
    *Npdsplay dll

    * If the menu bar is hidden then press and hold the Alt key down, that should make the Menu bar appear (Firefox 3.6 on Windows) (see [[Menu bar is missing]]).
    * Make sure that you have the ''Navigation Toolbar'' and other toolbars visible: View > Toolbars .
    * If items are missing then see if you can find them in the View > Toolbars > Customize window.
    * If you see the item in the Customize window then drag it back from the Customize window to the Navigation toolbar.
    * If you do not see that item then click the Restore Default Set button in the View > Toolbars > Customize window.
    See also [[Back and forward or other toolbar buttons are missing]] and [[Navigation Toolbar items]]
    See http://kb.mozillazine.org/Toolbar_customization

  • The browser back button is not working correctly when using the search funtion in ProBoards forums. Is there a known issue with ProBoards & FF?

    I have submitted a bug report to ProBoards, but they cannot duplicate the problem I am having, so I am submitting this here in hopes you can find a solution.
    At ProBoards Support and another PB forum while doing searches I found this problem, which continues with repeated testing over the past week or so:
    url: http://support.proboards.com/search
    1. enter perameters for the search (posts only by staff for the last 2 days)
    2. choose one of those post results & click on it (choose a post on page 14 and not on page 1 of the results)
    3. using the browser back button, attempt to return to the previous page of search results
    4. rather than being taken back to the search results with my parameters, the search parameters have been removed and the page show 1000 results of posts by everybody.
    I have tested this over and over again, disabling plugins, and nothing seems to alter the malfunctioning of the back button when I am doing this search function at ProBoards.
    I have tested it in Internet Explorer and find that in IE the browser back button works properly with ProBoards searches. I always get the result I expect, so it's a problem with how FF interfaces with ProBoards, I think.

    Many site issues can be caused by corrupt cookies or cache. In order to try to fix these problems, the first step is to clear both cookies and the cache.
    Note: ''This will temporarily log you out of all sites you're logged in to.''
    To clear cache and cookies do the following:
    #Go to Firefox > History > Clear recent history or (if no Firefox button is shown) go to Tools > Clear recent history.
    #Under "Time range to clear", select "Everything".
    #Now, click the arrow next to Details to toggle the Details list active.
    #From the details list, check ''Cache'' and ''Cookies'' and uncheck everything else.
    #Now click the ''Clear now'' button.
    Further information can be found in the [[Clear your cache, history and other personal information in Firefox]] article.
    Did this fix your problems? Please report back to us!

  • After updating IE7, Firefox 3.6 no longer store history--back button in Firefox can't access previous pages.

    Yesterday a security update for IE7 was automatically downloaded into my computer. Now the history feature of Firefox is working poorly. Often it doesn't save previous pages for the back button to access during an online session. The few times I've been able to navigate back to a Google search page, the search terms I've used previously are absent. However most often today, the browser doesn't even acknowledge that there were previous pages and the back button remains grayed out.

    I got an email saying that Cor-el had posted a reply to my question. I don't see it on this page. Was it deleted?

  • After doing a Google search, I click on a link and go to the searched web page.  When I go back to the Google page using the back button the links I originally clicked on no longer show as "greyed out".  Any idea what is going on with the browser?

    After doing a Google search, I click on a link and go to the searched web page.  When I go back to the Google page using the back button the links I originally clicked on no longer show as "greyed out".  Any idea what is going on with the browser?

    Type '''about:config''' in the Location (address) bar and press the "Enter" key. When you see a warning, click '''I'll be careful, I promise!''' button.
    * Preferences that have been modified are shown as '''bold (user set)'''.
    * Preferences can be '''Reset to the default''' or changed via the right-click context menu.
    -> In the '''Filter bar''', type '''browser.sessionhistory.max_entries'''
    * Right click the preference '''browser.sessionhistory.max_entries''' and click '''Modify'''
    * Change value from 0 to whatever you want over 0 (Default value is 50)
    * click OK
    -> Close the '''about:config''' tab and then Restart Firefox.
    See this post:
    * https://support.mozilla.com/en-US/questions/860894#answer-229574
    Check and tell if its working.

  • Updated to 3.0 - sluggish responses and "back" button no longer working?

    Hi all, first post - I'd like to know if others are having similar experiences after upgrading to 3.0 on a 2nd gen ipod touch.
    First off, when playing music, the "back" button always used to take me back to the previous song if the current song had only just started. However, now when I press "back", I get a random song, just like pressing "forward" in shuffle mode - so I cannot go back to re-rate a song for example. I want my "back" button back!
    Second, does anyone else find the responses to the "forward" and "back" buttons slow? There's like a half-second delay while the ipod "thinks" about performing the action, and before the screen updates (scrolls to the next album cover or details screen).
    Hoping there will be an official update ASAP to address these issues!

    Anytime you have problems like this, you should go through this routine:
    1. Restart your iPod - Hold the Sleep/Wake button down until you see the red slider - turn it off. To turn it back on, use the Sleep/Wake button and you will see an Apple icon as it restarts.
    2. Reset your iPod - Hold the Sleep/Wake button and the Home buttons down together until you see an Apple logo (takes about 10 seconds). Let your iPod restart.
    3. And finally, if those don't work for you, restore your iPod in iTunes. Everything will be wiped off and reloaded - and no, you won't lose anything.
    BTW, broken WiFi seems to be a very individual problem and there appear to be some work arounds. Battery life doesn't seem to be a general issue but again, an individual problem.

  • On 3 machines now the Windows Store is broken. The Install and Back buttons don't work

    Originally reported here:  http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_store/on-3-machines-now-the-windows-store-is-broken-the/8bafdc7a-a708-4012-a4f1-b98ab8788c28
    Advised to post here instead.
    Hi there
    On three separate Windows 8.1 Professional machines now, I've had an issue where the Store stops working properly for no apparent reason (no error messages or anything).  The store opens, and I can browse apps, and view individual apps, but
    once in the app view I cannot click on the Install button or the back buttons.
    They "light up" as if being pressed, but they don't actually do anything.
    I've tried all the various troubleshooting, including the Windows App troubleshooter, wsreset, re-registering the store files using powershell, and renaming the cache folder in my user profile. No effect.
    If I sign into the PCs as another user, then I don't get the issue. As such something is getting corrupted in the profile.
    We only have around 9 or 10 Windows 8.1 PCs deployed at our organisation for testing, and three of them have had this fault, which doesn't inspire confidence. As such, we cannot progress with further deployment until we have a fix in place that
    doesn't involve wiping the user profile.
    Any ideas please?

    Hi FangZhou CHEN
    I've discovered the cause of this error after much searching.
    Based on your suggestion, I checked the Event Viewer and found a string of "Application Error" entries similar to this:
    Faulting application name: WSHost.exe, version: 6.3.9600.17093, time stamp: 0x534765e9
    Faulting module name: sxwmon64.dll, version: 4.5.2608.0, time stamp: 0x52b2a853
    Exception code: 0xc0000005
    Fault offset: 0x00000000000257ff
    Faulting process id: 0xf40
    Faulting application start time: 0x01cfeeb1cc6d035e
    Faulting application path: C:\WINDOWS\WinStore\WSHost.exe
    Faulting module path: C:\WINDOWS\SYSTEM32\sxwmon64.dll
    Report Id: 19ee9a1c-5aa5-11e4-8259-600292638f85
    Faulting package full name:
    Faulting package-relative application ID:
    Presumably the WSHost,exe process is critical to the Store and "Metro" apps?
    The offending dll file causing this process to fail, sxwmon64.dll belongs to a peice of security software on our machines called Lumension Endpoint Security (we're running version 4.5 SR2). We use this to control removable media (USB) and CDRW access for
    our employees.
    If I rename that particular DLL file, the store and the calendar app which I was also having issues with (it was blank), spring back into life.

  • Firefox was a good, but now it's slow and when I search google I have to refresh the page when I click the back button. This is driving me to other browsers.

    When searching in goole, If I click on a link and want to go back a page firefox does not load the previous google search without refreshing the page. Because I use google frequently this is very annoying. Firefox has also been freezing and crashing most frequently of any of the other browsers that I have been driven to use. I'm not sure why I should keep it on my computer at this point.

    Regarding the Google results page blanking out when you go back, this occurs when using a combination of three settings, which may be fairly common:
    * Zoom level higher than two steps (120%; the newest versions of Windows apparently default to 125%, which Firefox detects and adopts)
    * Google search set to instant prediction results (default on Google search, but can be disabled in Search settings, see [https://support.google.com/websearch/answer/186610 Google Instant Search Help])
    * Opening results in the same tab, then using the Back button to return to the results page (default on Google search, but can be changed in Search settings to open results in a new window/tab, see [https://support.google.com/websearch/answer/425 Google Search Help])
    Firefox's cache feature attempts to maximize speed for forward and back actions by storing the last rendering of the page. Something about the instant prediction results ''with zoom'' is causing Firefox to briefly display the results and then they blank out and you have to reload the page to get them back. The mystery is why this only occurs (so far as I have heard) on Google? Is one of Google's scripts blanking out the page? Does Google care that it's messing up Firefox users?
    For now, if you do not want to or cannot change any one of the three factors needed to experience this problem, you can disable the storage of the last rendering of the page. Then Firefox will skip the shortcut and lay it out fresh, which is known to work. As noted in earlier posts, you make this change using the about:config preferences editor.
    (1) In a new tab, type or paste '''about:config''' in the address bar and press Enter. Click the button promising to be careful.
    (2) In the search box above the list, type or paste '''sess''' and pause while the list is filtered.
    (3) Double-click the '''browser.sessionhistory.max_total_viewers''' preference and change it to 0 (that's a zero).
    This thread has a lengthy discussion: [https://support.mozilla.org/en-US/questions/970863 When I go back to Google search results page, it takes me to a blank Google screen].

Maybe you are looking for