#15900: "Make the games list/filters using JavaScript ony"
Mille kohta see veateade on?
Mis juhtus? Palun vali alt
Mis juhtus? Palun vali alt
Palun kontrolli, kas samal teemal on juba aruanne olemas
Kui jah, siis HÄÄLETAGE selle raporti poolt. Kõige rohkem hääli sisaldavatele aruannetele antakse PRIORITEET!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detailne kirjeldus
-
• Kui näed ekraanil veateadet, kopeeri see siia.
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 -
• Kirjelda, mida sa soovisid teha, mida sa tegid ja mis juhtus
• mis on sinu veebilehitseja?
Chrome-based (Desktop, Mobile)
-
• Palun kopeeri/kleebi kuvatud tekst inglise keeles, mitte sinu oma keeles. 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. Kas see tekst on kättesaadav tõlkesüsteemis ? Kui jah, kas see on tõlgitud rohkem kui 24 tundi tagasi?
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 • mis on sinu veebilehitseja?
Chrome-based (Desktop, Mobile)
-
• Palun selgita oma ettepanekut täpselt ja lühidalt, et oleks võimalikult lihtne mõista, mida silmas pead.
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 • mis on sinu veebilehitseja?
Chrome-based (Desktop, Mobile)
-
• Mis oli ekraanil, kui sind blokeeriti? (Tühi ekraan? Osa mänguliidesest? Veateade?)
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 • mis on sinu veebilehitseja?
Chrome-based (Desktop, Mobile)
-
• Millist osa BGA kohandamisest ei järgitud
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 reeglite rikkumist on mängu taasesitusel näha? Kui jah, siis mitmendal käigul?
• mis on sinu veebilehitseja?
Chrome-based (Desktop, Mobile)
-
• Milline oli mängu tegevus, mida tahtsid sooritada?
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 -
• Mida püüdsid teha, et seda mängu tegevust käivitada?
-
• Mis juhtus, kui seda proovisite (veateade, mängu olekuriba teade, ...)?
• mis on sinu veebilehitseja?
Chrome-based (Desktop, Mobile)
-
• Millises mängu etapis esines probleem (Mis oli selle mänguetapi instruktsioon)?
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 -
• Mis juhtus, kui proovisite sooritada seda mängu käiku (veateade, mängu olekuriba sõnum, ...)?
• mis on sinu veebilehitseja?
Chrome-based (Desktop, Mobile)
-
• Kirjelda kuvamise probleemi. 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 • mis on sinu veebilehitseja?
Chrome-based (Desktop, Mobile)
-
• Palun kopeeri/kleebi kuvatud tekst inglise keeles, mitte sinu oma keeles. 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. Kas see tekst on kättesaadav tõlkesüsteemis ? Kui jah, kas see on tõlgitud rohkem kui 24 tundi tagasi?
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 • mis on sinu veebilehitseja?
Chrome-based (Desktop, Mobile)
-
• Palun selgita oma ettepanekut täpselt ja lühidalt, et oleks võimalikult lihtne mõista, mida silmas pead.
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 • mis on sinu veebilehitseja?
Chrome-based (Desktop, Mobile)
Aruande ajalugu
Lisa midagi sellele raportile
- Teine laua ID / käigu ID
- Kas F5 lahendas probleemi?
- Kas probleem esines mitmel korral? Igal korral?
- 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.
