#15900: "Make the games list/filters using JavaScript ony"
What is this report about?
What happened ? Please select from below
What happened ? Please select from below
Please check if there is already a report on the same subject
If yes, please VOTE for this report. Reports with the most votes are taken care of in PRIORITY!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detailed description
-
• Please copy/paste the error message you see on your screen, if any.
Currently the games overview page and filters make a request to the server, whenever a user starts filtering. This is propably unnecessary.
From what I see, you could reduce load, following an approach like this:
* Load the users games information (favorites,...) into local storage/ cookie (refresh from time to time, on change)
* Let the overview page and filters work in JavaScript only --> so no need for additional filter requests...
There are many JS libs for doing so, Isotope is a nice one: isotope.metafizzy.co -
• Please explains what you wanted to do, what you do and what happened
• What is your browser?
Chrome-based (Desktop, Mobile)
-
• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
Currently the games overview page and filters make a request to the server, whenever a user starts filtering. This is propably unnecessary.
From what I see, you could reduce load, following an approach like this:
* Load the users games information (favorites,...) into local storage/ cookie (refresh from time to time, on change)
* Let the overview page and filters work in JavaScript only --> so no need for additional filter requests...
There are many JS libs for doing so, Isotope is a nice one: isotope.metafizzy.co • What is your browser?
Chrome-based (Desktop, Mobile)
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
Currently the games overview page and filters make a request to the server, whenever a user starts filtering. This is propably unnecessary.
From what I see, you could reduce load, following an approach like this:
* Load the users games information (favorites,...) into local storage/ cookie (refresh from time to time, on change)
* Let the overview page and filters work in JavaScript only --> so no need for additional filter requests...
There are many JS libs for doing so, Isotope is a nice one: isotope.metafizzy.co • What is your browser?
Chrome-based (Desktop, Mobile)
-
• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)
Currently the games overview page and filters make a request to the server, whenever a user starts filtering. This is propably unnecessary.
From what I see, you could reduce load, following an approach like this:
* Load the users games information (favorites,...) into local storage/ cookie (refresh from time to time, on change)
* Let the overview page and filters work in JavaScript only --> so no need for additional filter requests...
There are many JS libs for doing so, Isotope is a nice one: isotope.metafizzy.co • What is your browser?
Chrome-based (Desktop, Mobile)
-
• Which part of the rules was not respected by the BGA adaptation
Currently the games overview page and filters make a request to the server, whenever a user starts filtering. This is propably unnecessary.
From what I see, you could reduce load, following an approach like this:
* Load the users games information (favorites,...) into local storage/ cookie (refresh from time to time, on change)
* Let the overview page and filters work in JavaScript only --> so no need for additional filter requests...
There are many JS libs for doing so, Isotope is a nice one: isotope.metafizzy.co -
• Is the rules violation visible on game replay? If yes, at which move number?
• What is your browser?
Chrome-based (Desktop, Mobile)
-
• Which was the game action you wanted to do?
Currently the games overview page and filters make a request to the server, whenever a user starts filtering. This is propably unnecessary.
From what I see, you could reduce load, following an approach like this:
* Load the users games information (favorites,...) into local storage/ cookie (refresh from time to time, on change)
* Let the overview page and filters work in JavaScript only --> so no need for additional filter requests...
There are many JS libs for doing so, Isotope is a nice one: isotope.metafizzy.co -
• What do you try to do to trigger this game action?
-
• What happened when you try to do this (error message, game status bar message, ...)?
• What is your browser?
Chrome-based (Desktop, Mobile)
-
• At which step of the game did the problem occurs (what was the current game instruction)?
Currently the games overview page and filters make a request to the server, whenever a user starts filtering. This is propably unnecessary.
From what I see, you could reduce load, following an approach like this:
* Load the users games information (favorites,...) into local storage/ cookie (refresh from time to time, on change)
* Let the overview page and filters work in JavaScript only --> so no need for additional filter requests...
There are many JS libs for doing so, Isotope is a nice one: isotope.metafizzy.co -
• What happened when you try to do a game action (error message, game status bar message, ...)?
• What is your browser?
Chrome-based (Desktop, Mobile)
-
• Please describe the display issue. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.
Currently the games overview page and filters make a request to the server, whenever a user starts filtering. This is propably unnecessary.
From what I see, you could reduce load, following an approach like this:
* Load the users games information (favorites,...) into local storage/ cookie (refresh from time to time, on change)
* Let the overview page and filters work in JavaScript only --> so no need for additional filter requests...
There are many JS libs for doing so, Isotope is a nice one: isotope.metafizzy.co • What is your browser?
Chrome-based (Desktop, Mobile)
-
• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
Currently the games overview page and filters make a request to the server, whenever a user starts filtering. This is propably unnecessary.
From what I see, you could reduce load, following an approach like this:
* Load the users games information (favorites,...) into local storage/ cookie (refresh from time to time, on change)
* Let the overview page and filters work in JavaScript only --> so no need for additional filter requests...
There are many JS libs for doing so, Isotope is a nice one: isotope.metafizzy.co • What is your browser?
Chrome-based (Desktop, Mobile)
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
Currently the games overview page and filters make a request to the server, whenever a user starts filtering. This is propably unnecessary.
From what I see, you could reduce load, following an approach like this:
* Load the users games information (favorites,...) into local storage/ cookie (refresh from time to time, on change)
* Let the overview page and filters work in JavaScript only --> so no need for additional filter requests...
There are many JS libs for doing so, Isotope is a nice one: isotope.metafizzy.co • What is your browser?
Chrome-based (Desktop, Mobile)
Report history
Add something to this report
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appears several time? Everytime? Randomly?
- If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.
