Xeedle Questions

Greetings,

I have a few questions I'd like to clarify:

1. On the [xeedle.ai](https://xeedle.ai/) website, you mention support for Cypress, but in the extension, I only see Selenium and Playwright. Could you clarify this?

2. The side panel works well for element inspection. Is there a way to assign a keyboard shortcut to toggle the pointer and another to toggle the panel?

3. Would it be possible to select a specific screen area, similar to a screenshot, to capture only a region of the elements being inspected? and then download it?

4. What sets Xeedle apart from tools like SelectorsHub, TruePath, or ChroPath?

5. In the history How did you enable the preview? When I entered the history I only see a link to the website where I took the elements from

Thank you for your attention. Looking forward to your response.

Best regards.

Kind regards

First of all, I congratulate you on such a good tool, I would like to ask you several questions before purchasing.

1. Is the tool still in development?

2. Is there a development path and continuous improvement of the tool?

3. Is there a possibility of locating a support email to send them some notes and get a true response?

4. Is there a Changelog section to see what updates are being given?

I am very attentive to your responses, very kind.

This looks so cool!

Can we get HTML and CSS, or just Javascript, etc.?

Thanks!

ps. If I can get html and css this is an auto-buy, I'd even be an MRR customer!

What about fullscreen or partial overalys with tabbed content within the overlay?

Apart from that: What actually will I do with the generated file?
If I code an e.g. react app or whatever kind of app, I got my files and tests.

Then, your website either is using very bad engllish or very bad translators or the combination of both. It really hard to guess what your messaging is but its clear you are prooud of your extension. But what does it actually do and how does it fit into any developer worlkflow (even your blog posts are so generic, they even don’t cover your own solution).

Honestly. Testing is great. Whatever gives me better testing I “auto love”. Please help explaining your solution & how it integrates into any real life dev workflow or CI/CD & Testing Framework.

BTW: Which testing framwork?

I'm a bit puzzled (not too many pieces, so there's still hope...) regarding the audience segment(s) who would 'undeniably' benefit from all of the features in Xeedle.
That comment seemed to be a fairly broad-brush stroke, so let me fill in some details:
I'm NOT a CODER. But I am 'hot on the hunt' for tools that leverage my inability to code.

With that said, I've purchased many CODE writers or APP Builders here on Appsumo.
I'm 'fair-to-partly-confident' in the selection of tools I've acquired (mechanics toolbox?).

Am I correct in stating (or maybe asking) whether Xeedle is for web scraping? Maybe?
Or maybe not? If not, what capacity (degree) of scraping can it perform to obtain code?

What then, lies within these opportunities, do holders have for possessing such CODE?
I was hoping that between the lines (of CODE,-Heaven's to Betsy), that it has an inkling website (or API) scraping? Or did I hit the proverbial 'bottom of the barrel' (in scraping)?