# html parser. Some elements missing.

**URL:** <https://forum.knime.com/t/html-parser-some-elements-missing/22133>\
**Category:** Community Extensions\
**Tags:** palladian-selenium\
**Created:** [March 30, 2020, 6:21am UTC](https://forum.knime.com/t/html-parser-some-elements-missing/22133 "2020-03-30T06:21:42Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![tebaldir](https://forum-cdn.knime.com/letter_avatar_proxy/v4/letter/t/b19c9b/32.png) [@tebaldir](https://forum.knime.com/u/tebaldir)\
**Post date:** [March 30, 2020, 6:21am UTC](https://forum.knime.com/t/html-parser-some-elements-missing/22133/1 "2020-03-30T06:21:42Z")

</div>

Hello,

I’m tring to get the results of a table in an html

 ![html parsed_vs_original](https://forum-cdn.knime.com/uploads/default/original/2X/4/4f9eee9bf15c549255b302dfe6ac091ef2128ab5.png) web page. I used the palladian html retriever and parser. I have the Problemthat some elements in the parsed html source are missing. in the picture you can see the difference between the parsed html in KNime and the original one from google Chrome.

Do you know if there is a solution or an ylternative way to get this table ?

Thank you,  
Roberto

here the workflow too.[KNIME\_html.knwf](https://forum.knime.com/uploads/short-url/xdq2M7pBJxg9Ug3r2ugZYO3JLNv.knwf) (12.0 KB)

---

<div class="post-metadata">

**Author:** ![AlexanderFillbrunn](https://forum-cdn.knime.com/user_avatar/forum.knime.com/alexanderfillbrunn/32/357_2.png) [@AlexanderFillbrunn](https://forum.knime.com/u/AlexanderFillbrunn)\
**Post date:** [March 30, 2020, 7:01am UTC](https://forum.knime.com/t/html-parser-some-elements-missing/22133/2 "2020-03-30T07:01:11Z")

</div>

Hi,  
can you try with the [Webpage Retriever](https://kni.me/n/_8Xu5w4lsg_0hzf3) node instead? I have used that one successfully before.  
Kind regards  
Alexander

---

<div class="post-metadata">

**Author:** ![qqilihq](https://forum-cdn.knime.com/user_avatar/forum.knime.com/qqilihq/32/50_2.png) [@qqilihq](https://forum.knime.com/u/qqilihq)\
**Post date:** [March 30, 2020, 7:34am UTC](https://forum.knime.com/t/html-parser-some-elements-missing/22133/3 "2020-03-30T07:34:15Z")

</div>

The mentioned parts are generated through JavaScript, so you will not get them with the HTML Parser (or any other static parser). For alternative approaches, I suggest to check the following link (even though the website is probably not AngularJS-based, the same principle applies):

> [@Scraping an AngularJS Website Post Load](https://forum.knime.com/t/scraping-an-angularjs-website-post-load/17781):
>
> Hello Everyone, Was wondering if someone could help. I am trying to scrape an angularJS website. When using the HTTPRetriever it only scrapes the HTML without the variables names written in/still has only placeholders. Was wondering if anyone knows how to work around this. Is there a way to allow for the page to fully load? A special trick to retrieving xpaths for Angular websites? Preferably without having to use a selenium node but that might be overly picky. Thanks in advance!

– Philipp

---

<div class="post-metadata">

**Author:** ![tebaldir](https://forum-cdn.knime.com/letter_avatar_proxy/v4/letter/t/b19c9b/32.png) [@tebaldir](https://forum.knime.com/u/tebaldir)\
**Post date:** [April 7, 2020, 3:53pm UTC](https://forum.knime.com/t/html-parser-some-elements-missing/22133/4 "2020-04-07T15:53:18Z")

</div>

Hi Philipp,

thank you for the suggestion. May be it works but I have a Problem with the Chromedriver. I can’t change the path on our Enterprise Computer so it doesn’t work.

May be you have a suggestion where can I copy the chromedriver without changein the path so that it works with selenium ?

thank you,  
Roberto

---

<div class="post-metadata">

**Author:** ![qqilihq](https://forum-cdn.knime.com/user_avatar/forum.knime.com/qqilihq/32/50_2.png) [@qqilihq](https://forum.knime.com/u/qqilihq)\
**Post date:** [April 7, 2020, 7:58pm UTC](https://forum.knime.com/t/html-parser-some-elements-missing/22133/5 "2020-04-07T19:58:36Z")

</div>

Hi Roberto,

it shouldn’t be necessary to change the path to the chromedriver, just leave it empty and the plugin will use the included binaries which are shipped with the installation (to clarify, the Chrome **driver** is not Chrome itself). Just make sure that Chrome is installed on the system.

If this is not possible, you can install the optional “Selenium Nodes for KNIME: Chromium” (needs to be explicitly selected during install). This will install an embedded Chromium instance which you can select in [“WebDriver Factory”](https://nodepit.com/node/ws.palladian.nodes.selenium.factory2.WebDriverFactory2NodeFactory) node.

In case you’re still facing obstacles, let me know!  
Philipp

---

<div class="post-metadata">

**Author:** ![tebaldir](https://forum-cdn.knime.com/letter_avatar_proxy/v4/letter/t/b19c9b/32.png) [@tebaldir](https://forum.knime.com/u/tebaldir)\
**Post date:** [April 8, 2020, 6:54am UTC](https://forum.knime.com/t/html-parser-some-elements-missing/22133/6 "2020-04-08T06:54:43Z")

</div>

Hi Philipp,

many thanks, With Chromium it works! Thank you.

P.S.:The standard Chrome installation didn’t work because of our Enterprise restriction. Error: “Loading of unpacked Extensions is disabled by the administrator”.

This ma help someone with the same “Enterprise” Problems.

Roberto

---

<div class="post-metadata">

**Author:** ![qqilihq](https://forum-cdn.knime.com/user_avatar/forum.knime.com/qqilihq/32/50_2.png) [@qqilihq](https://forum.knime.com/u/qqilihq)\
**Post date:** [April 8, 2020, 7:10am UTC](https://forum.knime.com/t/html-parser-some-elements-missing/22133/7 "2020-04-08T07:10:07Z")

</div>

Great to hear it works with the included Chromium. Thanks for the feedback!

---

<div class="post-metadata">

**Author:** ![system](https://forum-cdn.knime.com/uploads/default/original/1X/ab3ccf34482a0329361734a18199390177204f15.png) [@system](https://forum.knime.com/u/system)\
**Post date:** [April 21, 2023, 9:39pm UTC](https://forum.knime.com/t/html-parser-some-elements-missing/22133/8 "2023-04-21T21:39:23Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
