Google Chrome bug?

[joy]

I received an update notification too, but when I went back a few minutes later to download it, the message had disappeared from the Check for Updates dialog: No updates are currently available.

[shannong]

For those of us who implemented the manual workarounds when this issue first hit, what exactly do we need to "back out" when upgrading to the newest version of Flare? would presume that the following steps should be done, but it's worth double-checking here...

1. Remove the @namespace declaration at the top of the master project CSS (because Flare now inserts this same declaration at run time if you leave a default target option enabled). I'm presuming we don't want a "double instance" of this declaration?
2. Remove the "empty" CSS statement that we added before the default BODY {...} statement (this should no longer be needed and might confuse the parser)?

I must say I'm saddened that you chose to implement your permanent fix with an HTTP callout to your namespace XSD file, for reasons I list above in this post above in this thread. How do we get our hands on a downloaded version of that XSD so that we can include it in our project resources and point to it instead of the live version over the Web?

[MattyQ]

1. Remove the @namespace declaration at the top of the master project CSS (because Flare now inserts this same declaration at run time if you leave a default target option enabled). I'm presuming we don't want a "double instance" of this declaration?
2. Remove the "empty" CSS statement that we added before the default BODY {...} statement (this should no longer be needed and might confuse the parser)?

For what it's worth, I didn't need to remove the reference. Flare recognized it was already present and did not add a second instance of it. I never needed to add that empty statement, so I can't advise on that.

[shannong]

@ MattyQ: My instance of Flare 11.1.0 doesn't think there's an update available yet, so I haven't been able to test for myself.

@MadCap staff: I just checked with our chief architect about the xmlns: that points to your hosted schema. He said that he didn't think this would flag anything in a Salesforce security review, and was a supported feature in Salesforce in general. So please disregard my comments about this in previous posts.

[rob hollinger]

Flare 11.1.2 is now available.

Additional information can be found here:
http://kb.madcapsoftware.com/Content/Fl ... _Notes.htm

When you open Flare, you will be prompted to install the update.
This update is cumulative and will bring all 11.x.x versions to the current version.

For this Chrome issue, there are 2 options.
By default the name space will be injected in to the CSS at compile time.
There is also an option in the Target > Advanced tab to "Remove MadCap Styles". This will remove the MadCap Namespace from the css which means the namespace link is no longer needed.

[ChoccieMuffin]

Just to keep up with the latest versions I updated, but now the icon I have in my taskbar is some Windows default rather than the green Flare icon.

I know this is REALLY picky, but can anyone tell me how to get my Flare icon back?

[Gewesen]

@ ChoccieMuffin:
This worked for me:
1. Delete old icon from taskbar.
2. Navigate to Start menu.
3. Right click Madcap Flare tile, then select Pin to taskbar.
4. Navigate to your desktop and move the Flare taskbar icon to its proper place in the taskbar.

[jencasty9]

I have Flare 9, and I added the fix manually. The hover issue has been solved, but some of my styling are gone now? Can anyone help me with this issue?

[jencasty9]

Never mind, I fixed it by adding the code to the stylesheet after generating the output.

[ChoccieMuffin]

@ ChoccieMuffin:
This worked for me:
1. Delete old icon from taskbar.
2. Navigate to Start menu.
3. Right click Madcap Flare tile, then select Pin to taskbar.
4. Navigate to your desktop and move the Flare taskbar icon to its proper place in the taskbar.

Just back in work today - thanks, that worked a treat.

[ToddPh]

I had this problem fixed using the remedies in this thread and have installed the update to Flare 11 when it came out. All was good.

Today I am getting numerous queries from my internal customers because the problem is back on the two external customer sites I built using Flare. And during review-writing week. I must have ticked someone off big time to get this karma.

Has anyone seen this problem come back even with the fixes in place? I have a support ticket opened, and I'm questioning our internal server team to see if any changes were made.

I'm asking to see if anyone else has done any troubleshooting similar to this that might help me resolve the problem faster for my customers. Thanks!

[ToddPh]

Mystery solved.

Our server admins moved the production server and used an older version of the site. As I was fixing the problem on the old server, the changes never appeared on the public site. They have been suitably chastised for not including me and everything is ok again. Please disregard.