I am working on a web app that utilizes jquery UI for drag/drop functionality.
There's a strange problem in IE browsers only. When user drops an item inside a container, that item is added to the container but also leaves a remnant of it on the page.
Here's a working DEMO.
Drag items from the left column to yellow field to create container.
Add second item to newly created container.
What's causing it and how can I fix it?
This happens in IE8 and below.
The error is:
SCRIPT5007: Unable to get value of the property 'options': object is
null or undefined jquery-ui.min.js, line 105 character 158
That line is:
var a=d(this).data("draggable").options;
The jQuery UI version they are using is 1.8.11.
I would suggest upgrading to the latest version of jQuery UI and see if that resolves your issue.
If not, you might want to create a test case and submit it to them as a bug.
Related
I am using Maximo 7.6.1.1 and Birt (eclipse 4.3.1). The requirement is to add some page related text with a field from the report into the footer on each page, so I am attempting to update the master page footer. The master page is local, not extended.
I have tried to repeat this from 2013 (https://www.youtube.com/watch?v=lw_k1qHY_gU&t=4s) without success.
So using page level variables as described by the link did not work - it appears that the page event for the variable I chose (when the variable is about to be updated on the page) did not seem to be getting invoked.
Has this possibly changed (since 2013) or does someone know of another work around?
I tried to add a number of data elements to the footer without success.
I did see that if I added a value to the footer element in the initialization event for the report, that we could see that but we never got any updates even though the field we wanted to use was updated as it is normally.
I don't know Maximo, but these page variables only work if BIRT is running in 2 steps: RunTask, then RenderTask. If the program is using the single-step RundAndRenderTask, page variables don't work. This behaviour has not changed with "newer" BIRT releases.
I have a project which is using Umbraco v7.7.9 installed with nuget.
I was wondering if it is possible to change the buttons displayed in the sidebar section when a user selects to preview a content node. Particularly I want to remove the option that allows the user to close the preview.
The reason I want to hide this option is because some of the content the backoffice users will be previewing will not actually be published yet so clicking the close preview button causes an error.
I first asked this question on the Umbraco forums but haven't received a response yet, here is the link to the question: https://our.umbraco.org/forum/extending-umbraco-and-using-the-api/90878-editing-preview-window-sidebar-options
Thank you in advance.
Currently no - it would not be possible without doing hacks in the Core that would be overwritten when you upgrade your site (unless you manually merge your changes in when updating).
If you however don't mind doing that - the file used for the preview function is /umbraco/preview/index.html. You should look for the element with an exitPreview() click handler attached to it.
In later versions (7.10+) this modification will have to be done in /umbraco/Views/Preview/Index.cshtml instead, as these static files will be changed to MVC actions.
Update It appears I have to rebuild/redeploy the app to see the changes. Anyone know why I have to do this? It's a static .xhtml page. Coming back to update, looks like I just have to stop/restart the server, not a rebuild. I was dumb and didn't try that first, mostly because I have to rebuild/deploy often anyways.
I'm working on a JSF 2 app that uses f:subviews. I'm on one subview where my changes aren't reflected in the UI when I refresh the browser. I've worked on other subviews where I don't have this problem.
I have a batch script which copies my .xhtml files into my installed apps folder. The batch script reports the file is copied over. It's business as usual... If I drill down into this particular installed app, I see my change in the file. Again, seems like business as usual. The change is not reflected in the UI when I refresh, however.
These are simple text changes I'm making, but not seeing.
The problematic subview doesn't appear to be anything special, it's just a p:datatable that's included via a ui:include with a couple of parameters for the data and to give it a unique id. If I replace the p:datatable with just simple text, the "old" table still shows up in the UI when I refresh. I just can't get any changes in this subview to be reflected in the UI.
Console doesn't throw any errors.
I'm using WebSphere 7.0.
Never encountered this problem before. It isn't a browser caching issue as I can edit other subviews and see those changes when I refresh the page.
Anyone have any ideas?
While doing same testing with Geb in a Grails application, the tests passed when runned with default's HtmlUnitDriver.
But, when I changed to ChromeDriver, I was receiving
org.openqa.selenium.InvalidElementStateException: Element is not
currently interactable and may not be manipulated
when testing the login page.
The exception was thrown immediately after setting the emailField (selected through its id '#username'). The strange thing was that I was seeing the browser setting the value on the field, but after that (and before executing the following line of the code) it throwed the Exception.
I noticed that the login page had 2 elements with id="username" (one of which was a hidden field), and that was the reason of the exception. When I changed the id of the login page to another value (and updated the selector), the problem was solved.
I was getting the same exception when I was trying to access a text field on popup window.
org.openqa.selenium.InvalidElementStateException: Element is not currently interactable and may not be manipulated
I realized that the window is shown in two places and verified that indeed the Xpath being used to identify the text field on popup window was showing me two results in the FireBug+FirePath Plugin.
I updated the Xpath such that it would uniquely identify text field on the second popup window and the issue was resolved.
I have an xul overlay based Firefox Add-on that works. It has inline options defined in content/options.xul and they display/function correctly when the user goes to Firefox->Add-ons->Extensions->{The Name of My Extension}->Options
The question, can I a create a button on my Add-on that will launch my options either by taking the user to Firefox->Add-ons->Extensions->{The Name of My Extension}->Options with one click or by launching a dialog based on options.xul?
Right now I am maintaining a separate options.html and options.js that gets and sets the same settings that options.xul handles when the user navigates there via the Firefox button but I would much rather dump options.html and options.js and only maintain my main.js and options.xul.
Any comments or code examples will be greatly appreciated.
This is easiest to do via a global function BrowserOpenAddonsMgr() defined in the browser window, like this:
BrowserOpenAddonsMgr("addons://detail/" + encodeURIComponent(addonID));
This function takes care of focusing the existing add-ons tab if there is one or opening a new tab. It will not scroll down to the options however which is an issue if the add-on has a lengthy description. Starting with Firefox 12 this can be solved by adding "/preferences" to the view identifier:
BrowserOpenAddonsMgr("addons://detail/" + encodeURIComponent(addonID) + "/preferences");
With older Firefox versions you are out of luck (and you shouldn't use this suffix there, it won't work). The other issue is that there can be a lengthy "loading" phase where the add-ons manager fetches metadata for all extensions.