Text nodes cannot have margins or any other style applied to them, so anything you need style applied to must be in an element. If you want some of the text inside of your element to be styled differently, wrap it in a span or div, for example.
The element with text as Export is a dynamically generated element so to locate the element you have to induce WebDriverWait for the element to be clickable and you can use either of the Locator Strategies: Using CSS_SELECTOR: WebDriverWait(browser, 20).until(EC.element_to_be_clickable((By.CSS_SELECTOR, “a.layerConfirm>div[data-hover=”tooltip”][data-tooltip-display=’overflow’]”))).click() Using XPATH: WebDriverWait(browser, 20).until(EC.element_to_be_clickable((By.XPATH, “//button[contains(@class, ‘layerConfirm’)]/div[@data-hover=”tooltip” and text()=’Export’]”))).click() Note : You have to add … Read more
.container_12 .grid_6, .container_16 .grid_8 { width: 460px; } That says “make all .grid_6’s within .container_12’s and all .grid_8’s within .container_16’s 460 pixels wide.” So both of the following will render the same: <div class=”container_12″> <div class=”grid_6″>460px Wide</div> </div> <div class=”container_16″> <div class=”grid_8″>460px Wide</div> </div> As for the commas, it’s applying one rule to multiple classes, … Read more
NoSuchElementException org.openqa.selenium.NoSuchElementException popularly known as NoSuchElementException extends org.openqa.selenium.NotFoundException which is a type of WebDriverException. NoSuchElementException can be thrown in 2 cases as follows : When using WebDriver.findElement(By by) : //example : WebElement my_element = driver.findElement(By.xpath(“//my_xpath”)); When using WebElement.findElement(By by) : //example : WebElement my_element = element.findElement(By.xpath(“//my_xpath”)); As per the JavaDocs just like any other WebDriverException, … Read more
This error message… selenium.common.exceptions.NoSuchElementException: Message: no such element: Unable to locate element: {“method”:”name”,”selector”:”submitNext”} (Session info: chrome=66.0.3359.170) (Driver info: chromedriver=2.36.540470) …implies that the ChromeDriver was unable to locate the desired element. Locating the desired element As per the HTML you have shared to click on the element you can use either of the following Locator Strategies … Read more
The ~ selector is in fact the General sibling combinator (renamed to Subsequent-sibling combinator in selectors Level 4): The general sibling combinator is made of the “tilde” (U+007E, ~) character that separates two sequences of simple selectors. The elements represented by the two sequences share the same parent in the document tree and the element … Read more
Pekka’s answer is practically correct, and probably the best way to think about the issue. However, as many have already pointed out, the W3C CSS recommendation states that “Concatenating the three numbers a-b-c (in a number system with a large base) gives the specificity.” So the geek in me just had to figure out just … Read more
See adjacent selectors on W3.org. In this case, the selector means that the style applies only to paragraphs directly following another paragraph. A plain p selector would apply the style to every paragraph in the page. This will only work on IE7 or above. In IE6, the style will not be applied to any elements. … Read more
If I read the specification correctly, no. You can match on an element, the name of an attribute in the element, and the value of a named attribute in an element. I don’t see anything for matching content within an element, though.
> is the child combinator, sometimes mistakenly called the direct descendant combinator.1 That means the selector div > p.some_class only matches paragraphs of .some_class that are nested directly inside a div, and not any paragraphs that are nested further within. This implies that every element matching div > p.some_class necessarily also matches div p.some_class, with … Read more