IE History bug

In short:
I have an .aspx page that contains a flash object, using
swfobject, that communicates with the page via javascript. When
clicking the back button in IE it takes me two pages back, and not
to the previous page.
Details:
We use eclipse with FDT plugin to develop our flash apps in
AS2. I’m sitting with a problem when I’m communicating
a lot with IE using javascript. In normal scenarios the old getURL
is sufficient, but we’ve discovered that when you have a lot
of calls IE doesn’t handle it to well. So we use a queue
solution with the setinterval to give it a short breather, and it
works like a charm.
The scenario on the page is a search button….the search
brings back the results in href style and the user can then browse
to the relevant answer. If he doesn’t like it he will push
the Back Button on the IE browser. Now it jumps back two pages, so
you have to type in the search criteria again. If you push it
again, it goes to the page it should have gone to!
It seems that the history stack goes funny in IE as soon as
we have a flash component that does a lot of talking. If we remove
the flash object it works fine. There is no bug in the code as we
use this getURL() everyday…it’s just when we have a lot
of JS communication.
Have any of you come across something like this?
If so…solution?
Or any ideas?
Thanks!
PS: Firefox works 100%

Hello,
Make the MCUF_layout_11.gif 627px wide instead of 637px wide.
Just change the width in the properties window for this
temporary test.
Does it still drop now?
If so, how about 617px...
Take care,
Tim
"liveonnoevil" <[email protected]> wrote in
message
news:g23njm$dlo$[email protected]..
>I am having a problem in ie 6 and i cant figure out which
bug it is. can
> anyone help point me to the right place to start
looking? heres a link to
> the
> site;
>
>
http://www.mcuf.org/test/index.html
>
> heres a link to images of how it looks in ie7;
>
>
http://www.mcuf.org/test/example_ie7.jpg
>
> ie 6;
>
>
http://www.mcuf.org/test/example_ie6.jpg
>
>
>
http://www.mcuf.org/test/base_style.css
>
> any suggestions??
>

Similar Messages

  • File History Bug - Retains Only Last Version of Each File

    I've just discovered what I believe to be a serious bug in File History on Windows 8.1.  Here's what's happening:
    My files are backed up using File History on a 1TB external USB hard drive with 17.5GB free.  Currently 9GB of selected documents, etc., is being backed up and the aforementioned free space is what is available after 9GB has been backed up.  My
    File History settings are pretty normal / default.  It backs up every hour.  However, I've set it to keep saved versions 'until space is needed'.  I noticed recently that, despite having plenty of free space, File History has only been retaining
    the last copy of each of my backed up files.  It didn't communicate this to me, e.g., via an error.  I just happened to look to see how many versions were being retained.
    I've played around with it a bit to investigate.  First I blew away my FileHistory folder on the external drive and also the FileHistory folder from my user profile cache then set File History up again from scratch.  I then ran a completely fresh
    backup and changed some files and ran File History again.  This did not fix the bug.  File History was still retaining only the last file version and not notifying me of why or of any problem.  I checked the FileHistory-Core and FileHistory-Engine
    logs and, of course, no relevant errors were logged (typical for Windows event logs by the way).  
    I then tried changing the retention setting from 'until space is needed' to '1 year' and tested again by changing files and running File History.  It appears to be retaining earlier versions and working now.  
    This definitely looks like a bug to me.  Have Microsoft confirmed this and are they working on a fix ?
    It makes me wonder if File History keeps a large free space threshold when you specify 'until space is needed', e.g., 10GB or 1% of drive size.  When free space drops below this value, only one backup copy (the last one) is retained for each file.  Is
    this the case ?  Why doesn't it communicate this to the user ?
    Details:
    O/S: Windows 8.1 Pro x64 (upgraded in-place from 8.0)
    HDD: Western Digital MyBook 1TB (no 3rd party software installed for this).
    "Keep a cool head and always carry a lightbulb."

    Hi,
    Windows use this following API to determine if previous retention should be deleted:
    FH_RETENTION_TYPES which specifies under what conditions previous versions of files and folders can be deleted from a backup target
    The operating system deletes previous versions from a backup target only when the target is full.
     According to your description, your external drive should be less than 10% free space, this is a low disk space warning in system.
    Above, this is just my hypothesis, I did some test in my environment, when the disk free space is more than 10%, I can see multiple versions of file history, but when it is less than 10%, it would just keep the latest modification version.
    Alex Zhao
    TechNet Community Support
    Thanks for clarifying this Alex.  I still consider this a bug / design flaw in Windows as it is pruning backups long before the drive is actually full.  If there is, as you say, a large 10% low space threshold, the system should communicate to the
    user that it is pruning all but one copy of backup files.  Could this be logged as a bug please ?
    "Keep a cool head and always carry a lightbulb."

  • Lightroom 2.1 History Bug with Edited File

    I downloaded Lightroom 2.1 and now when I edit a file in Photoshop and then it comes back into Lightroom, if I click on one of the Presets, such as a B&W preset, then there is no way to get back to the edited file in color. The first entry in the History is the B&W preset, and I can't undo past that point to return to the color version of the edited file.
    Seems like it's not making a "edit in photoshop" history item that allows me to return to the original.

    I'm back trying to sort this problem out (got distracted for a couple of days by trying to get my monitor calibrated).
    Rearranging the folder structure didn't help. But I now have a better organized catalog, so that's ok :)
    What I did find is that if I import files into lightroom using the "file/import photos from device", then I can edit them normally afterwards (that is, when I save the file in photoshop cs3, the new file gets picked up correctly by lightroom and gets correctly stacked with the original). This is true even if the new files get added into the same directory structure that I'm having troubles with.
    So it looks like the directory structure is a red herring. It looks like the problem is in the catalog, with the way that lightroom originally imported my files. I created my original catalog by allowing lightroom to read my elements 6 catalog.
    It seems that I have this edit problem with all catalog entries that were imported from elements 6, but I don't have any problem with catalog entries that lightroom brings in directly (either through "import photos from device" or by adding a new folder to the lightroom catalog).
    So right now it looks like there is a problem with the elements catalog conversion.
    Is this a problem that anybody else has seen? Any suggestions for getting around it?
    Doug

  • History bug in Safari with latest update?  (10.4.8)

    It seems Safari is only remembering a day or two worth of history since the latest upgrade (10.4.8). I've cleared the cache, deleted the Safari preferences, etc... No good. This was never an issue prior to the upgrade.
    Any ideas? It's really driving me nuts.

    My History shows 5 days of activity. Have not seen any post on this board since the update describing a similar problem to Safari's History.
    Have you modified the History parameters (number/days etc.) using a 3rd party application such as Safari Enhancer?
    iMac G5 Rev C 20" 2.5gb RAM 250 gb HD/iBook G4 1.33 ghz 1.5gb RAM 40 gb HD   Mac OS X (10.4.8)   LaCie 160gb d2 HD Canon i960 printer

  • Colour history bug

    If you grab a colour out of your history, then alter it the new colour isn't saved to the history. As the colorpicker has been removed (very annoying), it makes it almost impossible to recreate a colour created in this way. Can this get fixed (or better, bring back the picker)

    Hi,
    I have tried to reproduce this behavior but cannot reproduce this problem. After picking a color, changing it through the "Color Wheel", and making some strokes in the canvas, I can see the new color in the "Color History", please see attachment :
    Thanks,
    Jose

  • To XMP or not to XMP

    I was bitten by the Lightroom 5.0 History bug (images developed in earlier versions of Lr lost complete histories if the history state was changed in the Develop module) and was able to recover because I had good backups.  I've updated to 5.2 since, so I don't expect to run into that again.  One thing I noticed during my recovery operation is that Lr will warn me if there is a mismatch between metadata in the catalog and metadata in the image file.  Overwriting the metadata in the image with the metadata in the recovered catalog fixed the some issues with the effects of the bug, but it got me thinking -- what if the metadata hadn't been written to the image file at all?
    I'm more of a video guy than a photo guy, and I set up Lr to automatically write metadata to the files because that's what I do for my video files when I use Premiere Pro.  But I think my recovery would have been easier and less stressful if I hadn't had to see or base a decision on the intimidating metadata mismatch warning that Lr presents.
    So I'm asking for general opinions -- what do you think about the pros and cons of having Lr automatically write metadata to XMP?
    Jeff

    Samoreen wrote:
    But you will regularly forget Ctrl-S anyway .
    Actually, I never forget. Or perhaps I should say if ever I do forget, it will be caught.
    There are two times I save metadata:
    1. When I've done enough editing I'd be bummed if it got lost, but I'm not finished yet.
    2. When I'm finished.
    finished means "finished for now" - most photos are published after they're finished, and re-published after they're finished again...
    In the former case (1), I just don't worry about it too much, in the latter case (2) it's done as part of a "finalization ritual" which (takes snapshots of and also) assigns metadata to finished photos... I use the ChangeManager plugin for that, but there is more than one way to accomplish a goal. For example, Jeffrey Friedl has Folder Status plugin for "managing change" on a folder basis instead of photo basis. You can also follow a self-designed procedure which does not require plugins.
    The concept is: once saving xmp becomes part of a workflow that includes assigning (and/or clearing) metadata, it's the assigned (or cleared) metadata that drives the relationship (status) between catalog settings and xmp on disk.
    I turn xmp status indicators off, and rarely look at the metadata status collection(s). Why?
    1. They sometimes say metadata needs to be saved when it doesn't.
    2. They sometimes say metadata wasn't saved when it was.
    3. They may seem to indicate you should read metadata when you shouldn't.
    4. Metadata conflict status depends on date/time only, not contents, and so many "conflicts" are simply false alarms.
    etc.
    i.o.w. it's never been a reliable (nor robust) feature in Lightroom, and I just don't need it, since I have other "metadata status" metadata that I have complete control of, which *is* reliable.
    If I ever get confused, ChangeManager's "Compare Catalog to Disk" feature gives a complete list of all differences between develop settings and metadata in catalog and those in xmp on disk.
    I don't necessarily recommend everybody do things how I do them, since my way (although robust) employs plugins - it's not "as simple as possible", and there is something to be said for simplicity.
    My main point is that if you can figure a way to assure xmp is saved when appropriate, manual method may be best.
    If you can't or just don't want to, then auto method may be best for you. And of course there are those that rely on the catalog exclusively and never save xmp - that's another way to go.
    UPDATE:
    =======
    Perhaps the most important aspect to me of saving manually: I want to save (finalized) xmp only after scrutinization, since part of the goal is NOT to save screw-ups in xmp! - they're already in the catalog .
    =======
    Rob
    Message was UPDATED by: Rob Cole

  • BUG: File History fails with no warning- Event ID 201

    I apologize for the long post but I want to summarize everything I've learned about this so far, as it looks like a critical bug.
    I am unable to get File History to backup my files with Windows 8.1.  I set up a 1 TB USB HDD as the target drive and it seemed to run for a minute or two, and then quit completely without any warning.  It created two empty folders on the target
    HDD, but no data was backed up.  I then clicked "Run Now" to try and get it going again, but nothing happened. 
    Under "Advanced Settings" I opened the event log, and saw an Event ID 201 was created each time File History attempted to run: "Unable to scan user libraries for changes and perform backup of modified files for configuration C:\Users\MyUserName\AppData\Local\Microsoft\Windows\FileHistory\Configuration\Config". 
    I've pasted the entire error below.  The "Event Log Online Help" link opens to "Page not Found" on TechNet.
    A Google search revealed other users are experiencing this problem, too (links below).  Some people have been able to solve it by excluding libraries and/or moving all of their data out of the libraries then replacing it one folder at time, running
    FH, and repeating until they find the "offending" file by error 201 occurring.
    There are reports of similar problems with Event IDs 202, 203 and 204.   A similar, but separate error is "Unusual condition was encountered during scanning user libraries for changes and performing backup of modified files for configuration C:\Users\MyUserName\AppData\Local\Microsoft\Windows\FileHistory\Configuration\Config". 
    Based on others' posts, the problem appears to be a bug in how FH handles files/folder names that are similar,
    contain unusual (but legal) characters, and shortcuts ("reparse error").   The second bug is, regardless of which Event ID, that
    FH does not alert the user when it fails, so you have no idea your files are not being backed up.  Even if you are able to eliminate the problem once, there is no guarantee that it won't happen again.  Once error 201 occurs, File
    History is dead in the water and unfortunately since Windows 7 File Backup was removed, there is no alternative data backup method available.
    If anyone has an idea of how to solve or work around this problem (i.e. under exactly what filename conditions FH fails), please post.  I have Windows 8.1 installed on drive C, Windows 7 on drive D, and a data partition E onto which I moved all my Libraries. 
    The Win 7 and 8.1 libraries are in separate folders and not linked in any way, so 8.1 is not trying to back up 7's data.  However, the partition arrangement does not appear relevant.
    Thanks!
    Related links:
    http://answers.microsoft.com/en-us/windows/forum/windows_8-files/filehistory-unable-to-scan-user-libraries-for/b43183bc-eeaa-4d1a-bda4-0ab9dcf061be
    http://social.technet.microsoft.com/Forums/windows/en-US/ccd27fbc-2d95-4ab7-bdd1-2c0c6a43bd2f/file-history
    My Event Log:
    Log Name:      Microsoft-Windows-FileHistory-Engine/BackupLog
    Source:        Microsoft-Windows-FileHistory-Core
    Date:          4/3/2014 11:01:19 PM
    Event ID:      201
    Task Category: None
    Level:         Error
    Keywords:      
    User:          SYSTEM
    Computer:      ThinkPad-Edge
    Description:
    Unable to scan user libraries for changes and perform backup of modified files for configuration C:\Users\inert_000\AppData\Local\Microsoft\Windows\FileHistory\Configuration\Config
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-FileHistory-Core" Guid="{B447B4DB-7780-11E0-ADA3-18A90531A85A}" />
        <EventID>201</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x1000000000000000</Keywords>
        <TimeCreated SystemTime="2014-04-03T14:01:19.267846200Z" />
        <EventRecordID>12</EventRecordID>
        <Correlation ActivityID="{388E273A-4F3D-0001-022B-8E383D4FCF01}" />
        <Execution ProcessID="556" ThreadID="5128" />
        <Channel>Microsoft-Windows-FileHistory-Engine/BackupLog</Channel>
        <Computer>ThinkPad-Edge</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="Hr">2147747327</Data>
        <Data Name="ConfigFilePath">C:\Users\inert_000\AppData\Local\Microsoft\Windows\FileHistory\Configuration\Config</Data>
      </EventData>
    </Event>

    Hi, thanx for the post. It helped me to fix my Problem with file history.
    In my case it was the spelling of some files. I'm German and we have some Special chars like ä,ö,ü and ß.
    The "Problem" is that You can spell These also in a different way for example "ä" is same like "ae" and "ß" is same like "ss" .
    If I Name one file like "groß.txt" and the other one "gross.txt" file history won't work! I don't know why, probably MS conversts the Name in the background or whatever - but this really
    sucks!
    Even more that You don't get informed! Only when checking the eventlog - and not even in the "normal" eventlog - You have to go to "Microsoft-Windows-FileHistory-Engine/BackupLog" - well, how often does one look up this??
    I think file history is quite useless in this state as it does not inform the user about Problems with the backup. And I really don't want to get "informed" when I Need to restore some files...
    Cheers
    To life is christ, to die is gain...

  • Bug: For a migrated roaming profile from V2 to V3 browser history may not work ...

    Solution: Do a new profile ...
    or
    use the bug fix from Win8 and previous:
    https://social.technet.microsoft.com/Forums/ie/en-US/6418ae13-63c7-44a1-9e97-0ad875a2bd7a/browsing-history-not-being-recorded?forum=ieitprocurrentver#d16f8580-0d2a-40f7-8197-86d232bbaa74
    Try this ....
    Problem:
    C:\users\%username%\appdata\local\Microsoft\Windows\history is lacking the +S (system attribute)
    Test:
    > Desktop > File Explorer > \users\appdata\local\Microsoft > Shift+Right Click on Windows Folder > Open new command prompt > attrib History
    The result you get back in the command window should read something like this (Note the "S" to left):
       S    I    C:\Users\%username%\AppData\Local\Microsoft\Windows\History
    Fix:
    > \users\appdata\local\Microsoft > Shift+Right Click on Windows Folder > Open new command prompt > attrib +S History
    ... and History comes back in IE:
    > Desktop > IE to confirm.
    Reason:
    A Bug in Windows (or Windows 8 ... seen this issue posted quite a few times for Windows 8.
    I'm actually able to recreate the issue persistently with domain accounts and roaming profiles on a second login on any Windows 8 system. The issue is there after the local profile has been ("re")created on that system. I don't why it happens
    ... but it happens every time for domain account.

    Thank you for your answer.
    The entry in that registry key remains indeed there. Is it safe to just remove that registry key when the user is no longer logged into that specific server?
    The KB that you have send me is with the following explanation:
    Notes
    This issue occurs when the Windows Search service is enabled.
    When this issue occurs, the registry subkey that represents the stale user profile is deleted. This subkey appears in the following location:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
    But we do not have the Windows Search service installed nor is it enabled in the services list? But the subkey does remain in the registry.
    With kind regards,
    Thijs

  • [svn] 4910: Implementing workaround for history manager rendering issue ( Firefox/Mac) caused by a long standing player bug.

    Revision: 4910
    Author: [email protected]
    Date: 2009-02-10 11:51:58 -0800 (Tue, 10 Feb 2009)
    Log Message:
    Implementing workaround for history manager rendering issue (Firefox/Mac) caused by a long standing player bug.
    Bugs: SDK-17020.
    QE Notes: None
    Doc Notes: None
    Reviewer: Alex
    Tests: DeepLinking
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-17020
    Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/managers/BrowserManagerImpl.as
    flex/sdk/branches/3.x/templates/html-templates/client-side-detection-with-history/history /history.js
    flex/sdk/branches/3.x/templates/html-templates/express-installation-with-history/history/ history.js
    flex/sdk/branches/3.x/templates/html-templates/no-player-detection-with-history/history/h istory.js

  • When clearing all recent History, data in find menu is not cleared. Is this a bug?

    When clearing all recent History, data in find menu is not cleared. Is this a bug?

    Hi Tas_n,
    The following help page will help you clear the cache which will get rid of your search history.
    [https://support.mozilla.org/en-US/kb/How%20to%20clear%20the%20cache?s=cant+clear+Find&r=4&e=es&as=s How to clear the cache]
    Further down on the webpage this can be set to clear automatically.
    Kind regards
    bouncer1966

  • Ios safari clear history hold back button bug

    try to clear you hisotry
    go to safari
    hold the back button
    it will still sometimes show your history.
    i've tried this by clearing it through bookmarks and clearing through the general>settings menu and both have this bug
    is this just me or anyone else?

    this actually happens if you close your tabs still. It shows you what you were looking at even AFTER you cleared your history!

  • Fx 29 not terminating on exit unless clear history option is un-checked... fix this bug!

    Pre v29 this was not an issue. I have read all the threads on this bug, and none of the proposed solutions are acceptable. Mozilla needs to fix this bug. I have no intention of allowing my history to be retained when I exit the application. I am not absolutely certain that this is always the case, but this seems to happen when the browser has been opened from an email link. Come on, Mozilla. There are other browser options out there, and I am now seriously considering switching to one of them.
    rfcdvc

    hello, this is going to be fixed in the next version of the browser - for now you can run the firefox 30 beta version which should no longer be affected by this issue: https://www.mozilla.org/firefox/beta/

  • History in my search bar will not clear even though I have selected all the appropriate settings under tools/privacy etc. Is this a Firefox bug or am I doing something wrong?

    No additional details - just can't figure out why the search history will not clear.

    when i go to Music > Artist > All, as you suggested, i see all the albums i have listed. doesn't really relate to my problem with artists with songs in one album, as well as song w/o album set, and the latter not showing up.
    but that reminds me, why is it when i go to the All section from a particular artist and they do have more than one album (or even no albums), the order of the songs is in the order they are in the albums.. if i wanted the order it is on albums, i would have selected that album for example.. it would be nice if the songs were in alphabetical order when you're NOT browsing by album, making a particular song easier to find (what if you have thirteen albums for example and u aren't sure which album a song is on, now you have to scroll through a seemingly random ordered list to find one song, alphabetical would be SOOOO helpful!)

  • Image Processor.jsx bug (CS3, 10.0.1): fail to restore history item sometimes

    I have very limited history depth (5 items) to conserve my RAM.
    When I run "Image Processor" script, which calls some complex Action, "Image Processor" fails to restore history item (because it was dropped already) in this lines (tere is same line for every save file type):
    app.activeDocument.activeHistoryState = historyState;
    This line(s) throw exception (file was saved, really!), and file remains open and after processing 10-15 files computer starts to thrash.
    I've surrounded all these lines with try { ... } catch(e) {} and it works for me.
    IMHO, it here are two bad ideas in this script:
    (1) Consider every and any exception as error. In this case, history is not a thing I care about
    (2) Don't close files in case of error. It can fill up RAM & scratch disk very quickly.

    Update Server
    Try:
    - Powering off and then back on your router.
    - iTunes for Windows: iTunes cannot contact the iPhone, iPad, or iPod software update server
    - Change the DNS to either Google's or Open DNS servers
    Public DNS — Google Developers
    OpenDNS IP Addresses
    - For one user uninstalling/reinstalling iTunes resolved the problem
    - Try on another computer/network
    - Wait if it is an Apple problem

  • Lightroom 3 - not inserting history steps bug(?)

    Sometimes I'll do a series of edits quickly and LR3 will make them but not show them in the history panel. I've grabbed screenshots here of one case, where I imported a photo, rotated it slightly and bossted exposure. Both edits were made as you can easily see in the image, but the rotation wasn't recorded in history.
    I use an autohotkey script to give keyboard shortcuts for some things that don't have a built in shortcut so I can make some edits very fast, maybe the history panel isn't keeping up with the edits properly?

    Thanks! Can't believe I didn't check that in the first place. Turns out my K20D's raw files are a few pixels off being exactly 3:2 (4672x3704, which works out as 3.01:2 )

Maybe you are looking for