I am facing a strange issue, Below are the steps to reproduce it
Close all instances of a browser (any) and then run the below link, notice that the styles don't get applied.
https://libenc.iaea.org/iii/encore/home?lang=eng&suite=def&advancedSearch=true&searchString=
Go to this link in adjacent tab - https://libenc.iaea.org/iii/encore/?lang=eng
Now, refresh the page with the first link, the styles gets applied.
If you compare the page source at stage 1. and stage 3., you can notice that the source in 3. contains these additional includes
What is causing this to happen? Is there any way to have these styles included while at stage 1.?
I don't have access to modify these pages since its hosted by another vendor.
UPDATE:
Below is almost exactly similar link from another user of the same vendor which works perfectly.
http://encore.lipscomb.edu/iii/encore/home?lang=eng&suite=cobalt&advancedSearch=true&searchString=
Related
I am using Google Analytics on a Sharepoint site. On the main page, we have an image in an image carousel that once clicked will bring you to a different page on the site. I have tried everything to track clicks on this image in GTM - click url, click ID, css selector, etc. I can not figure out why my trigger never fires. I have attached the
image, what pops up when I click inspect, and variables that show up with the click in GTM preview... (This is the second half of the variables in preview).Three images total.
Good job on including all the relevant debugging info.
Judging from your inspect, you're looking at the image.
However, judging from your click event inspection, the click lands on an a.
I don't see the a in your DOM on the screenshot, but it may be either dynamically added, or just outside of the screenshot.
No matter. Let's start to carefully debug it. Make a trigger that would be triggered on anything that matches a. That's just a debugging trigger. Make sure it triggers on your image clicks.
Now, let's just make a simple CJS variable that would console.log({{Click Element}}). No need to use it anywhere, just make it. Go to the debug view again, try clicking the banner again and look in the console for something that would look like this:
See that pretty element? Now the wonderful dev console allows you to copy JS path to this element and do whatever you want with it. Mainly, comfortably and quickly test CSS selectors against this element. I suggest changing the selector JS console generated. It should work (unless the page is too dynamic), but it would be fragile. Having the element, however, you'll be able to make your own selectors.
I'm working on an application that has many links. They all open in the same window, until today. All of a sudden, in all browsers I'm testing in, 3 links in an iframe or object (I've tried both) start opening in a new window. I can't seem to stop this.
An object example follows. The dolnks program generates 3 simple links like the one following the object example and these links open in a new window.
<OBJECT ID='fixed' DATA='dolnks.cgi?str=$params' TARGET='dynamic' NORESIZE></OBJECT>
darea.cgi?str=$dogstr
Can someone help me understand this and how to get these links to open in the same window.
All links that now open in the same window or should be opening in the same window are from
the same domain.
I now have to close the link instead of using the back button.
Thanks,
craigt
I imagine it's because of your TARGET attribute, although it's not using one of the special target values:
target
Where to display the linked URL, as the name for a browsing context (a tab, window, or ). The following keywords have special meanings for where to load the URL:
_self: the current browsing context. (Default)
_blank: usually a new tab, but users can configure browsers to open a new window instead.
_parent: the parent browsing context of the current one. If no parent, behaves as _self.
_top: the topmost browsing context (the "highest" context that’s an ancestor of the current one). If no ancestors, behaves as _self.
From the MDN Docs: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#attributes
Note though that the docs for object do not list a target attribute, so that behavior is apparently undefined, and probably varies depending on the browser, and the plugin displaying the object.
Check to see if it's the items with a target attribute (case does not matter) that are working "wrong", and see if removing that attribute fixes it. If that's not it, next check to see if there are javascript being loaded. Try turning javascript off (hopefully the relevant links are not generated with javascript) and see if that fixes the behavior. If turning javascript off is too heavy handed, you can use the javascript console to see what listeners are attached to the links.
When I'm in Access and using a Tab Control, if I copy a button on one tab and paste it to the same tab, this button becomes visible on all tabs. In fact, I think all controls do (I know it happened with buttons and labels).
Is there a way to fix this, or do I have to delete the copied controls and re-draw them on the tab they're supposed to be visible on? Is there a setting that fixes this? I've got a few pages where it'd be handy to be able to copy a chunk of controls and paste them onto a different tab.
This is an old issue that needs to be closed out. The OP #Johnny Bones talks about his answer in the comments but never posted what he did to fix it as an answer.
The answer is that the object was pasted in at the wrong level, the form level. Form level objects are seen on every Tab Page.
To fix this
Cut the object again
Select the Tab Page you want the object to live inside
Paste it there
Move it to the correct location
I'm building a webcrawler using Selenium Webdriver with Chrome. It uses
links = self.browser.find_elements_by_xpath("//*[#href]")
gets all the links on a page and then loops through the links to filter them. However, on every site I've tested, once it gets to a certain link on a certain page, it stalls at this line:
url = link.get_attribute("href")
It's not an error, it just stops, as if it hit an unending loop. For a given site, it's always on the same link on the same page for every test run. The stalling does not occur with Firefox - everything works fine. However, I need it to do this using Chrome for other reasons (trust me on this).
The version of Chrome I'm using is 28.0.1500.52, and I'm using the latest Chrome driver, which is compatible with that version. What could be going on here?
EDIT (IGNORE THIS EDIT)
After looking into it some more, I've found what's causing the problem: There's a part further down in the code that mouses over every link that's found.
hov = ActionChains(self.browser).move_to_element(link)
hov.perform()
When I comment that part out, it works. Now I have to figure out why this should have any effect on getting the href attribute from a Selenium link object (especially when it works fine for the first arbitrary number of link objects)...
EDIT 2
Ignore the first edit.
I've been working on a new website and practicing my JS/jQuery/AJaxy skills. Last night I wanted to take a look at how long the page was taking to render and see if there were any areas I could clean up to increase speed. While the page loads in about 200 - 300 ms every time, I'm seeing a large amount of blank space between resource loads under the network inspector.
http://i.imgur.com/7ng6m.jpg
Has anyone else seen this or know what I can do to minimize that time (talking about the blank space between like the html and the first css file)?
Quite possibly it is caused by the extensions you have installed. AdBlock, LastPass and Google quick scroll took altogether about 200 ms on my machine.
Unfortunately, these extensions are invoked on every site and block loading the additional resources.
Try it with out of the box browser setup, the loading time will increase tremendously.
You've got a bunch of images loaded just after the page has been loaded (the load and DOMContentLoaded events have fired - the blue and red vertical lines across the Timeline). I can see that the images are loaded by the JQuery library (the Initiator column), perhaps to build a gallery or something.
So, the case is that JQuery loads the images after the page load, presumably in the onload handler (this can look like $(document).ready(handler) in your code, but other options are possible, too).
The delay between the initial page load and requesting the first resources is almost certainly caused by Chrome extensions. To find the culprit: Record a timeline in the Timeline tab in Chrome Developer Tools; Identify the scripts that are running during the Parse HTML phase; Work out which extensions they're from.
To record a timeline:
Open the timeline tab and click record.
Reload the page and then stop the recording. (A couple of seconds should be enough.)
To find the culprit:
Find the first main Parse HTML block on the timeline. On the row below you will probably see one or more Evaluate Script blocks. These are the culprits.
Click on one of the Evaluate Script blocks and find the script name in the bottom pane. Mouse-over the script name. The tooltip will have the URL of the script, which should be of the form chrome-extension://{long_identifier}/{path}
Memorise the first few letters of the identifier and search for it in the chrome://extensions/ page. This tells you which extension is causing the problem. Try disabling it - you should see a difference.
Repeat for the other Evaluate Script blocks.
In my case, I have 20 extensions installed but only two were causing a delay: LastPass and Fauxbar. I've chosen to leave them enabled because for me the productivity benefit of these extensions outweighs the downside of the added latency.