Monalisha Nanda
Firstly very nice work done...It is really helpful
I am writing below some points for improvements:
1. The xpath generated in some pages are somehow little clumsy.. It is difficult to identify which xpath is for which Element
2.Once if we have all the xpaths generated in one page and user is again clicking on AXG extension it is generating xpath again and it happens multiple time. Somehow we can deny to generate the xpath in one page if it is already generated for that page.
3. When we click on any xpath to copy it remain highlighted..It is confusing to say whether the xpath is copied or not if we again click on highlighted xpaths. We can give a text "copied to clipboard" and a copy icon beside xpath
4. There should be some options if we have copied the xpath we could remove it from the page. Sometimes we navigate to other pages and some xpath still remains in the some section of the page
|
Krishna Kumar
Good Initiation and the thought is nice as it is showing all the XPaths just next to the element. I hope there are so many updates coming in the near future as it is just created and launched it seems.
I request other people also try and provide the feedback to improvise this extension.
|
Chr Pqe
There is a little problem with this extension. If I open it on, for example, Google's homepage, it will show all the Xpaths, but unfortunately with a useless //a[text="....."] format. The problem with this Xpath is that it is pointless to use it to automate because website link text (for example Google's homepage) change all the time, to it will make automating not working... Is is possible to force the extension to use a more classic approach (CSS, or better again tags)
|
Monalisha Nanda
Firstly very nice work done...It is really helpful
I am writing below some points for improvements:
1. The xpath generated in some pages are somehow little clumsy.. It is difficult to identify which xpath is for which Element
2.Once if we have all the xpaths generated in one page and user is again clicking on AXG extension it is generating xpath again and it happens multiple time. Somehow we can deny to generate the xpath in one page if it is already generated for that page.
3. When we click on any xpath to copy it remain highlighted..It is confusing to say whether the xpath is copied or not if we again click on highlighted xpaths. We can give a text "copied to clipboard" and a copy icon beside xpath
4. There should be some options if we have copied the xpath we could remove it from the page. Sometimes we navigate to other pages and some xpath still remains in the some section of the page
|
Krishna Kumar
Good Initiation and the thought is nice as it is showing all the XPaths just next to the element. I hope there are so many updates coming in the near future as it is just created and launched it seems.
I request other people also try and provide the feedback to improvise this extension.
|
Chr Pqe
There is a little problem with this extension. If I open it on, for example, Google's homepage, it will show all the Xpaths, but unfortunately with a useless //a[text="....."] format. The problem with this Xpath is that it is pointless to use it to automate because website link text (for example Google's homepage) change all the time, to it will make automating not working... Is is possible to force the extension to use a more classic approach (CSS, or better again tags)
|
Monalisha Nanda
Firstly very nice work done...It is really helpful
I am writing below some points for improvements:
1. The xpath generated in some pages are somehow little clumsy.. It is difficult to identify which xpath is for which Element
2.Once if we have all the xpaths generated in one page and user is again clicking on AXG extension it is generating xpath again and it happens multiple time. Somehow we can deny to generate the xpath in one page if it is already generated for that page.
3. When we click on any xpath to copy it remain highlighted..It is confusing to say whether the xpath is copied or not if we again click on highlighted xpaths. We can give a text "copied to clipboard" and a copy icon beside xpath
4. There should be some options if we have copied the xpath we could remove it from the page. Sometimes we navigate to other pages and some xpath still remains in the some section of the page
|
Krishna Kumar
Good Initiation and the thought is nice as it is showing all the XPaths just next to the element. I hope there are so many updates coming in the near future as it is just created and launched it seems.
I request other people also try and provide the feedback to improvise this extension.
|
Chr Pqe
There is a little problem with this extension. If I open it on, for example, Google's homepage, it will show all the Xpaths, but unfortunately with a useless //a[text="....."] format. The problem with this Xpath is that it is pointless to use it to automate because website link text (for example Google's homepage) change all the time, to it will make automating not working... Is is possible to force the extension to use a more classic approach (CSS, or better again tags)
|
Monalisha Nanda
Firstly very nice work done...It is really helpful
I am writing below some points for improvements:
1. The xpath generated in some pages are somehow little clumsy.. It is difficult to identify which xpath is for which Element
2.Once if we have all the xpaths generated in one page and user is again clicking on AXG extension it is generating xpath again and it happens multiple time. Somehow we can deny to generate the xpath in one page if it is already generated for that page.
3. When we click on any xpath to copy it remain highlighted..It is confusing to say whether the xpath is copied or not if we again click on highlighted xpaths. We can give a text "copied to clipboard" and a copy icon beside xpath
4. There should be some options if we have copied the xpath we could remove it from the page. Sometimes we navigate to other pages and some xpath still remains in the some section of the page
|
AutomaticXpathGenerator
