Timeline for 'OpenCalloutAndSelectItem' is undefined / 'ShowMenuForTrOuter' is undefined
Current License: CC BY-SA 3.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 9, 2014 at 15:16 | history | edited | axawire | CC BY-SA 3.0 |
Including real answer from comments.
|
Jun 9, 2014 at 13:16 | vote | accept | thanby | ||
Jun 9, 2014 at 13:15 | comment | added | thanby | I removed my jQuery reference and let the Brava one take over and things are working again! Granted a couple other errors popped up as a result but those will be for another question because I'm not sure if they're directly related. Thanks for the help! I'll accept your answer, can you edit it to add this specific solution so if someone searches for it they'll have the actual answer up top, not down here in the comments? | |
Jun 6, 2014 at 20:10 | comment | added | axawire | I would test the solution with JQuery commented out in the master page first, see if it even works. I think if things break at a later date because Brava is removed it is going to be easier to find the comment/problem in the master page than issues that show up because .ready() isn't working properly when JQuery was loaded after the javascript check on the couple of pages that end up using it. bugs.jquery.com/ticket/2509 they closed the bug, but I think they basically gave ways to work around it and documented it as behavior by design. | |
Jun 6, 2014 at 19:49 | comment | added | thanby | So you're saying I can work around it but even that solution is going to be problematic? Is the only complete solution to remove jQuery from my custom master pages all-together? | |
Jun 6, 2014 at 18:50 | comment | added | axawire | You could use javascript to check if JQuery is already loaded. Do the check after Brava should have loaded it and if its not loaded then load it. You will probably run into issues though with JQuery code that uses .ready() on the page. | |
Jun 6, 2014 at 18:32 | comment | added | axawire | If you remove the JQuery reference from the master page and the Brava for SharePoint solution is not incorporated on every page then any page that was expecting JQuery will no longer have it automatically from the master page. | |
Jun 6, 2014 at 18:19 | comment | added | axawire | I agree "GET /_catalogs/masterpage/Site/js/jquery.min.map HTTP/1.1 returning a 404" is unrelated to your problem. | |
Jun 6, 2014 at 18:18 | comment | added | axawire | JQuery is usually minified when deployed so it will have variables like a, b, c instead of meaningful words for variables. The dev tool you are using is probably expected this map file that would allow it to give you the more meaningful variable names when looking inside the JQuery source. A user not using the dev tool wouldn't have the file requested and so would not get the 404. | |
Jun 6, 2014 at 17:35 | comment | added | thanby | As far as I can see there's nothing interrupting the js files from being loaded with one exception (logged in Fiddler) "GET /_catalogs/masterpage/Site/js/jquery.min.map HTTP/1.1" is returning a 404. Unfortunately I don't see how this one could be connected. I have some more information about the situation from another party, I'll add it to my question, maybe it will help spot the missing/bad function. By the way, skel.js doesn't include hoverIntent as far as I can see. | |
Jun 4, 2014 at 20:41 | history | answered | axawire | CC BY-SA 3.0 |