I'm having a really weird problem. When I click on Quick View the first time on
http://coderweb.info/tbps/index.php/shop/accessories
the content appears in the modal window as it should, namely once. The second time I click on any of the Quick View buttons, it appears twice (except for the image). The third time it appears thrice and so on. There is no loop anywhere in the code. The Quick View link is in the following format
http://coderweb.info/tbps/index.php/shop/accessories/universal-dual-tone-horns-detail?how=quick&tmpl=component
It basically loads the Virtuemart Product Detail page, but I have modified it so that when the 'how' parameter is passed with the value 'quick', it shows the 'Quick View' instead:
if(JRequest::getVar('how','') == 'quick'){
echo $this->loadTemplate('quick');
return;
}
What is causing this problem? How do I fix this?
I added
rel="{handler:'iframe'}"
to the link and that seems to have fixed it. I guess it was using a div element by default and it wasn't being cleared properly.
Related
My page is: https://www.svelysium.net/ And one can see the menu as a list flash first then display correctly. I'm testing visibility:none in the CSS for the div and then wanting to do an onload later for the visibility after the page loads so I don't get that menu flash. I've not put it up live because I can't seem to get it right. Sorry I can't find any examples of this issue and how to solve it and I have been trying to keep it simple. There must be an easy fix. Thanks in advance.
I want to be able to search right after the webpage is rendered, instead of click on the search box then start typing.
However when I trying to mimic focusInput in original source code, it doesn't work.
It could be reproduced by visit
https://ember-power-select.com/docs/multiple-selection
and run document.querySelector('.ember-power-select-trigger-multiple-input').focus() which is focus on an input tag.
I expected to see something like this
, but actually nothing happened.
I also tried to .click() on all parent html elements of that input, but nothing happened
Any help?
I would suggest a tabindex to you. When you set the tabindex to 1 the search field will be the first to focus.
As an alternative you can try to achive this with an application instance initializer. In it you can now select the proper element and set the focus on it.
I'm using Selenium to perform testing on BrowserStack, and have hit a problem while testing IE8.
I've found that when I target elements and then call Click, the full effect of the action is not being undertaken*.
Through trial-and-error I found that if I call Click twice then the expected action is undertaken.
However, one of the testing steps involves writing a number to a text field, and for this I have the following:
driver.FindElement(By.CssSelector("...")).Click();
driver.FindElement(By.CssSelector("...")).Clear();
driver.FindElement(By.CssSelector("...")).SendKeys(Keys.NumberPad1);
driver.FindElement(By.CssSelector("...")).Click();
But "1" never appears in the field. I can tell it never appears because I'm capturing screenshots after each step; I can see that the field gets highlighted (as the active element) and I can see the cursor inside the field, but no result from the method call.
Furthermore, I've even tried giving the field an ID and addressing it with
driver.FindElement(By.Id("txtCountManual")).SendKeys(Keys.NumberPad1);
But with the same (lack of) results.
Does anyone have any suggestions as to how I may send a textual value to a field in IE8 using Selenium and BrowserStack?
* The "expected action" involves using Knockout.js to display a selected value in another element. So for example, I found that if I programmatically click a radio button and then take a screenshot, I can see that the radio button has been clicked but the action performed by Knockout.js has not taken place; if I click the element a second time then the Knockout.js action is performed. This double-clicking is not required when I manually test using IE8 via BrowserStack.
To see the problem, please run the following in browser by clicking the arrow shown in upper right corner of of output panel.
http://jsbin.com/uVORASe/4/edit?html,js,output
Click one of the links (either strategy-1 or strategy-2) to display output generated by the child template. Then click back button on browser. When the back button is clicked, browser shows the parent URL as expected. But parts of the child display remains on screen. This process repeats every time a child route is visited. Why? Going back to the parent route should just display strategy-1 and strategy-2 on the left side.
I don't think this is an Ember-Data issue because problem also happens when I tried Ember-Model. I think use of the bootstrap classess has something to do with this. For example, if I take away the bootstrap table-responsive class, Ember throws an error.
Any ideas to explain what's going on?
The close tag of your <table> tag is wrong. You are using </table the expected is </table>.
http://jsbin.com/UKONORI/1/edit
When the user clicks the OK or APPLY button on a property sheet and the program determines data on some page is invalid, how can I cause the page containing the error to be displayed along with a message box describing the error?
Currently the procedure doing the validation does the following while processing the PSN_APPLY notification.
MessageBox (hDlg, "Data must be positive!", "Error", MB_OK);
SetWindowLong (hDlg, DWL_MSGRESULT, PSNRET_INVALID);
This works ok if the page doing the validation (A) is currently displayed but if some other page (B) is being displayed, the message box appears with that page (B) being displayed, then when the message box is answered, the page with the validation error (A) is displayed. I thought about setting some flag so that when that page (A) gets the PSN_SETACTIVE notification it displays the message box but that seems kind of hokey.
Win32 API in c++, no MFC, no NET, nothing fancy.
I think the problem is in the design of your validation and it's presentation.
Am I right in thinking that you iterate through your property sheets, validate them and display a message box if something is awry? Because of course, what you have witnessed will happen, if I am on property page 3 and I wrote crap in to a field on property page 1.
The easiest solution is, when validating, note which property page the field in question is, and set that one active if the user has written crap in to one of your fields. This seems the fastest way possible.
Also, rather than spring up an annoying message box, reserve some room beneath the property pages to display a textual (red or otherwise) warning as to why, and then change to the appropriate property page, and highlight the offending control. Your validation routine can do this nice and easily as it loops through.
Even better, don't stop at the first error. One thing I HATE is correcting one field that I think is the only issue, only to be told every time I hit "OK" or "SUBMIT" that there's something else I missed.
I seriously think you should consider going the extra mile here... loop through ALL controls, and add all invalid ones to a list. Then change each offending control's background colour, tab colour etc... Then the user can work through and correct, no matter how many errors he or she made.