#15900: "Make the games list/filters using JavaScript ony"
Apie ką šis pranešimas?
Kas nutiko? Pasirinkite iš žemiau esančio sąrašo
Kas nutiko? Pasirinkite iš žemiau esančio sąrašo
Patikrinkite, ar jau yra pranešimas apie tą patį dalyką
Jei taip, balsuokite už šią ataskaitą. Ataskaitos su dauguma balsų pateikiamos PRIORITETU!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detalus apibūdinimas
-
• Jei ekrane matote kokį nors klaidos pranešimą, įklijuokite jį čia.
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 -
• Prašome paaiškinti, ką norėjote padaryti, ką padarėte ir kas atsitiko
• Kokia tavo naršyklė?
Chrome-based (Desktop, Mobile)
-
• Prašome nukopijuoti / įklijuoti tekstą, rodomą anglų kalba, o ne savo kalba. 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. Ar šis tekstas yra translation system? Jei taip, ar jis buvo išverstas daugiau nei 24 valandas?
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 • Kokia tavo naršyklė?
Chrome-based (Desktop, Mobile)
-
• Prašome paaiškinti siūlomą pakeitimą tiksliai ir glaustai, kad būtų kuo lengviau suprasti, ką jūs siūlote.
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 • Kokia tavo naršyklė?
Chrome-based (Desktop, Mobile)
-
• Kas buvo pavaizduota ekrane, tave užblokavus (juodas ekranas? Nepilna žaidimo sąsaja? Klaidos pranešimas?)
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 • Kokia tavo naršyklė?
Chrome-based (Desktop, Mobile)
-
• Į kurias taisykles neatsižvelgiama BGA žaidimo versijoje
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 -
• Ar taisyklių pažeidimas matomas žaidimo atkartojime? Jeigu taip, kuris veiksmo numeris?
• Kokia tavo naršyklė?
Chrome-based (Desktop, Mobile)
-
• Kurį žaidimo veiksmą norėjai atlikti?
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 -
• Ką reikia padaryti, kad iššauktum šį žaidimo veiksmą?
-
• Kas įvyko kai bandei tai padaryti (klaidos pranešimas, žaidimo būsenos pranešimas, ...)?
• Kokia tavo naršyklė?
Chrome-based (Desktop, Mobile)
-
• Kuriuo žaidimo metu problema atsirado (koks buvo tuometinis žaidimo nurodymas)?
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 -
• Kas įvyko kai bandei atlikti žaidimo veiksmą (klaidos pranešimas, žaidimo būsenos pranešimas, ...)?
• Kokia tavo naršyklė?
Chrome-based (Desktop, Mobile)
-
• Aprašykite rodomą problemą. 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 • Kokia tavo naršyklė?
Chrome-based (Desktop, Mobile)
-
• Prašome nukopijuoti / įklijuoti tekstą, rodomą anglų kalba, o ne savo kalba. 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. Ar šis tekstas yra translation system? Jei taip, ar jis buvo išverstas daugiau nei 24 valandas?
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 • Kokia tavo naršyklė?
Chrome-based (Desktop, Mobile)
-
• Prašome paaiškinti siūlomą pakeitimą tiksliai ir glaustai, kad būtų kuo lengviau suprasti, ką jūs siūlote.
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 • Kokia tavo naršyklė?
Chrome-based (Desktop, Mobile)
Raportų istorija
Papildyti šį raportą
- Kitas stalo ID / ėjimo ID
- Ar F5 išsprendė šią problemą?
- Ar problemos atsirado keletą kartų? Kiekvieną kartą? Atsitiktiniu metu?
- 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.
