-
```
What steps will reproduce the problem?
1. Downloading a .zip of the new 1.7.0 version and running localhost for the
first time (on my Windows machine using GAE 1.9.8)
What is the expected output…
-
```
What steps will reproduce the problem?
1. Downloading a .zip of the new 1.7.0 version and running localhost for the
first time (on my Windows machine using GAE 1.9.8)
What is the expected output…
-
Initialize the PowerSearch with the current query profile. This means listening to 'eexcess.queryTriggerd' events and display the attributes in the corresponding fields.
-
The placement of the submit button looks a bit strange. Maybe you could place it in the center? Or at least include some margin to the border.
-
```
What steps will reproduce the problem?
1. Downloading a .zip of the new 1.7.0 version and running localhost for the
first time (on my Windows machine using GAE 1.9.8)
What is the expected output…
-
When removing tags from the input fields, those tags/terms are only removed on UI level, but are still included in the ajax-query to the recommender
-
```
What steps will reproduce the problem?
1. Downloading a .zip of the new 1.7.0 version and running localhost for the
first time (on my Windows machine using GAE 1.9.8)
What is the expected output…
-
```
What steps will reproduce the problem?
1. Downloading a .zip of the new 1.7.0 version and running localhost for the
first time (on my Windows machine using GAE 1.9.8)
What is the expected output…
-
```
What steps will reproduce the problem?
1. Downloading a .zip of the new 1.7.0 version and running localhost for the
first time (on my Windows machine using GAE 1.9.8)
What is the expected output…
-
The PowerSearch provides a TimeRange as Input but still gets connected to the Privacy-Proxy-1.0, which doesn't know any TimeRange.
The latest version of the Privacy Proxy would be helpful. (Deploymen…