> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/webcomponents-overview/faqs/questions-and-troubleshooting.md).

# Questions and troubleshooting

This page lists common questions and problems and their solutions.

<details>

<summary>Which version is the documentation referring to?</summary>

Latest.\
Always make sure you are using the latest version before opening inquiries.

</details>

<details>

<summary>Can I contribute to the future development of FactFinder Web Components?</summary>

You can discuss and propose issues, changes, and features at [GitHub issues](https://github.com/FACT-Finder-Web-Components/ff-web-components/issues).\
We are grateful for any feedback, so do not hesitate to ask questions or express concerns whenever you find something worth sharing.

</details>

<details>

<summary>Which browsers do FactFinder Web Components support?</summary>

FactFinder Web Components utilizes the Web Components Web API.\
Although some browsers may not support this standard in full, FactFinder Web Components only requires a basic set of functionalities of the standard which is supported by basically all browsers.

If you, however, notice compatibility issues, you have the option to use the official [Web Components polyfill](https://github.com/webcomponents/polyfills/tree/master/packages/webcomponentsjs#browser-support) which is provided with the FactFinder Web Components bundle.\
It guarantees support for *Chrome*, *Firefox*, *Edge*, *Safari 9+*, *Chrome Android* and *Mobile Safari*.

See [Setup with polyfill](broken://pages/403b411d9c43aed27e105cd90a41c7558ccf9534) for instruction on how to integrate with the polyfill.

</details>

<details>

<summary>How can I find out which data is available in a Web Component's HTML template?</summary>

Each FactFinder Web Component has a property that holds the data it is displaying.\
You can access its contents from the browser console.

Some examples:

```js
document.querySelector("ff-record-list").records
document.querySelector("ff-record").recordData
document.querySelector("ff-asn-group").group
document.querySelector("ff-breadcrumb-trail-item").breadCrumbIrailItem
```

Note that most browsers support the shortcut selector `$0` which references the element that is currently selected in the browser's dev tools' *Elements* tab.\
E.g.:

```js
$0.pagingItem
```

See the *API* tab of each element's page for available properties.

</details>

<details>

<summary>How frequently do you release breaking changes?</summary>

No more than once every six months.

Find the release date of the last `x.0.0` release and add six months to determine when a breaking release becomes possible.

Breaking changes are released as the need arises.\
Typically, this is much less frequent than six months.\
Emergency fixes that introduce breaking changes may be exempted.

</details>

<details>

<summary>I want to use FactFinder Web Components with another front end framework, but data bindings (`{{ }}`) in templates collide.</summary>

Typically, front end frameworks provide options to skip resolving particular data bindings.\
In Angular, for example, there should be the `ngNonBindable` attribute to prevent Angular from parsing double curly braces.\
Consult your framework's documentation for relevant information.

Alternatively, you can change the default data binding symbols that FactFinder Web Components uses.\
See the [Template Engine documentation](broken://pages/bbc1cc522c6acc6783bdf59a2c884e74a31c4f1c) article for details.

</details>

<details>

<summary>How to avoid crawlers indexing unresolved URLs `<a href="https://shop.com/%7B%7Bdata.binding%7D%7D">` which results in a 404?</a></summary>

Please use our `data-*` attributes for images and redirecting.

**For anchors use:**

```html
<ff-record-list>
  <template data-role="record">
    <ff-record>
      <div>
        <a
          data-redirect="{{record.variantValues.0.Deeplink}}"
          data-redirect-target="_blank"
          data-anchor="https://www.myshop.de{{record.variantValues.0.Deeplink}}"
        >
          Shop
        </a>

        For successful tracking, use the `data-redirect` attribute.
        Without it, the browser may redirect before tracking succeeds.

        For images, use:
        <img data-image="{{record.variantValues.0.ImageName}}">
      </div>
    </ff-record>
  </template>
</ff-record-list>
```

</details>

<details>

<summary>Hit highlighting in <code>ff-suggest</code> or <code>ff-asn-group</code> displays as raw HTML. How do I make it render correctly?</summary>

This usually occurs when a custom template uses double curly braces, `{{ }}`.\
Double curly braces render text as-is.

Use triple curly braces, `{{{ }}}`, to render the highlighting markup as HTML.

See [Hit highlighting](/webcomponents-overview/api/basic-elements/suggest.md#hit-highlighting) in the `ff-suggest` documentation or the [Template Engine documentation](broken://pages/bbc1cc522c6acc6783bdf59a2c884e74a31c4f1c).

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fact-finder.com/webcomponents-overview/faqs/questions-and-troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.