I am facing strange issue on Google Chrome, Firefox does not seems to be affected by this problem.
Reproduce problem
Go to http://twitter.github.io/bootstrap/javascript.html#typeahead
type any thing, such as A, once auto suggest appear, try, typing "&", it won't accept till auto suggest is displayed.
I tried Google-ing for it, but did not find any thing. also, it's not a reported problem : https://github.com/twitter/bootstrap/issues?labels=js&state=open
can someone confirm if they are also facing this issue? Or if it is already reported with Bootstrap.
Thanks in Advance
Ravish
Found solution:
I've reported this issue on Bootstrap's Github page: https://github.com/twitter/bootstrap/issues/8190
They have informed that Bootstrap Typeahead has been deprecated, and they plan to use Twiter Typehead going forward : http://twitter.github.io/typeahead.js/examples/
Twiter typehead does not contains above reported problem. Will be using Twitter Typehead instead Bootstrap Typehead.
Thanks.
Related
Something's wrong with babel issues on github.
https://github.com/babel/babel/issues redirects to https://github.com/babel/babel/pulls, direct links to issue (e.g. https://github.com/babel/babel/issues/2679) show 404 page not found.
Is this only me?
oh, look like they've moved the issues tracker to https://phabricator.babeljs.io/
direct links to issues became https://phabricator.babeljs.io/T${ID}, e.g. https://phabricator.babeljs.io/T2679
Currently I'm trying to upgrade the application from wicket 1.4 to wicket 6 and I'm stuck with the following issue:
When I try to close ModalWindow, it is closed but I receive PageExpiredException on the page where I was opening this ModalWindow, so I'm redirected to
/myapp/wicket/bookmarkable/org.apache.wicket.markup.html.pages.PageExpiredErrorPage
I thought maybe the way I create ModalWindow is outdated, so I've tried an example from here
http://www.wicket-library.com/wicket-examples-6.0.x/ajax/modal-window?0
and it gives me the same exception.
Maybe I have to configure something in my WebApplication implementation, but I don't know what.
If anyone could help, it'll be really appreciated. Thanks.
Check your server logs for errors related to the serialization of the opener page. PageExpiredException means that the page cannot be found in the page storage. If there was an error with the serialization then it won't be stored and thus later won't be found too.
I have downloaded the source project from
sourcecode.
I came across many issues over there, then I changed the source header path then changed the compiler version in the project settings, then all those were solved, now there is no errors, it runs, when I click FBLoginButton ,Facebook Login Dialog appeared but it looks empty,
I dont know why, The app key and app secret key were placed correctly.
I tried with device,if there would probm with simulator, still looks same.
what Im doing wrong, I had searched a lot, not found any solution, any ideas pls tell me
I have the same problem.
I have opened a bug here : https://developers.facebook.com/bugs/279606225487338
You can also vote for it, so that FB may take a look at it. Let's hope they solve it.
We had two apps in the app store which used this old api of facebook for login and they also g=have stopped working... So most probably Facebook has stopped support for this but I couldn't fond anything official. I guess we will have to incorporate the new Api.. :/ If I find something I will post here...
I have applications which are displayed as tabs in Facebook pages which have been working fine. They suddenly started displaying this output in the tab:
/1336720089,176820405/
if (window.CavalryLogger) { CavalryLogger.start_js(["EgxV3"]); }
__d("UFIUpdate",
Any ideas what is going on???
Here is a link to one of them: http://www.facebook.com/TweakShoes/app_132692060112327
A temporary solution is to add https:// to facebook itself. This doesn't solve the problem, but it'll allow you to see your page on a per client basis.
The best fix in the longer term until facebook fixes this issue is to go to your account settings > Security > Enable secure browsing. This will enforce HTTPS wherever it can and should resolve the issue for a lot of pages you're trying to access.
Good Luck!
After encountering this issue yesterday, I tracked it down to an apparent conflict with the JS log wrapper included as part of HTML5 Boilerplate's script.js file. In particular, the "make it safe to use console.log always" snippet. After commenting it out, the FB lib error went away and my app displayed properly.
I didn't dig into what the conflict was, but here is the snippet. If you use something similar on your page, then it may be worth investigating.
/* make it safe to use console.log always */
(function(b){function c(){}for(var d="assert,count,debug,dir,dirxml,error,exception,group,groupCollapsed,groupEnd,info,log,timeStamp,profile,profileEnd,time,timeEnd,trace,warn".split(","),a;a=d.pop();){b[a]=b[a]||c}})((function(){try
{console.log();return window.console;}catch(err){return window.console={};}})());
It's probably not a coincidence that FB's own logger bugs out with this.
Facebook has opened a bug for this issue and recently triaged it to medium priority - no word on when it will be addressed.
I have download the Whole code from JIRA Mobile connect's home site but
I have facing this issue while install the JIRA Mobile connect,All the things is perfect but in My project i have one JMCViewController.xib and it contain one scrollview and the class assign to that scrollview is JMCScrollViewContainer and that is missing so How to find that class, I have tried all the things but not get success so can any one solve this problem? Please help
Thanx in Advance for any Help Any Suggestion,
These classes were added recently so you will need to manually add them.
You can get them from here https://bitbucket.org/atlassian/jiraconnect-ios/src/0f2c90244acd/JIRAConnect/JMCClasses/Core/views