#15900: "Make the games list/filters using JavaScript ony"
Sobre qué é este informe?
Qué aconteceu? Por favor selecciona debaixo
Qué aconteceu? Por favor selecciona debaixo
Por favor revisa se xa hai un informe sobre o mesmo tema
De ser afirmativo, por favor VOTA por este informe. Aos informes con máis votos se lles da PRIORIDADE!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Descrición detallada
-
• Por favor, copia e pega a mensaxe de erro que ves na túa pantalla, se houbera algún.
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 -
• Por favor, explica o que querías facer, o que fixeche e o que pasou
• Cal é o teu navegador?
Chrome-based (Desktop, Mobile)
-
• Por favor, copia/pega o texto amosado en inglés no canto do teu idioma. Se tes unha captura de pantalla deste erro (boa práctica), podes usar un servizo de hospedaxe de imaxes da túa elección (snipboard.io, por exemplo) para subila e copiar/pegar o enlace aquí. É este o texto dispoñible no sistema de tradución? Se é así, foi traducido fai máis de 24 horas?
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 • Cal é o teu navegador?
Chrome-based (Desktop, Mobile)
-
• Por favor explica a túa suxestión de maneira precisa e concisa para que sexa o máis sinxelo posible entender o que queres dicir.
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 • Cal é o teu navegador?
Chrome-based (Desktop, Mobile)
-
• Qué había na pantalla cando se quedou bloqueado? (mensaxe de erro?, pantalla en blanco?, unha parte da interface do xogo?)
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 • Cal é o teu navegador?
Chrome-based (Desktop, Mobile)
-
• Qué parte das regras non se cumpriron na adaptación da BGA?
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 -
• é visible a violación das regras na repetición? Se o é, en que número de movemento?
• Cal é o teu navegador?
Chrome-based (Desktop, Mobile)
-
• Qué acción de xogo querías realizar?
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 -
• Qué é o que tratache de facer para activar esta acción do xogo?
-
• Qué sucedeu cando o fixeche (a mensaxe de erro, mensaxe na barra de estado do xogo, ...)?
• Cal é o teu navegador?
Chrome-based (Desktop, Mobile)
-
• En que paso do xogo ocorreu o problema (cal foi a instrucción actual do xogo)?
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 -
• Qué sucedeu cando tratache de facer unha acción de xogo (mensaxe de erro, mensaxe na barra de estado do xogo, ...)?
• Cal é o teu navegador?
Chrome-based (Desktop, Mobile)
-
• Por favor, describe o problema de visualización. Se tes unha captura de pantalla deste erro (boa práctica), podes usar un servizo de hospedaxe de imaxes da túa elección (snipboard.io, por exemplo) para subila e copiar/pegar o enlace aquí.
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 • Cal é o teu navegador?
Chrome-based (Desktop, Mobile)
-
• Por favor, copia/pega o texto amosado en inglés no canto do teu idioma. Se tes unha captura de pantalla deste erro (boa práctica), podes usar un servizo de hospedaxe de imaxes da túa elección (snipboard.io, por exemplo) para subila e copiar/pegar o enlace aquí. É este o texto dispoñible no sistema de tradución? Se é así, foi traducido fai máis de 24 horas?
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 • Cal é o teu navegador?
Chrome-based (Desktop, Mobile)
-
• Por favor explica a túa suxestión de maneira precisa e concisa para que sexa o máis sinxelo posible entender o que queres dicir.
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 • Cal é o teu navegador?
Chrome-based (Desktop, Mobile)
Historial de informes
Engade a este informe
- Outro DI de mesa / ID de movemento
- Premer F5 resolveu o problema?
- Apareceu o problema varias veces? Tódalas veces? Aleatoriamente?
- Se tes unha captura de pantalla deste erro (boa práctica), podes usar un servizo de hospedaxe de imaxes da túa elección (snipboard.io, por exemplo) para subila e copiar/pegar o enlace aquí.
