• אנא העתק/הדבק את הודעת השגיאה המופיעה במסך, אם יש כזו.

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

• בבקשה הסבר מה רצית לעשות,מה עשית ומה קרה

• מה הדפדפן שלך?

• בבקשה העתק והדבק את הטקסט המוצג באנגלית במקום בשפה שלך. 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. האם טקסט זה זמין במערכת התרגום? אם כן, האם היא תורגמה במשך יותר מ -24 שעות?

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

• מה הדפדפן שלך?

• אנא הסבר את ההצעה שלך במדויק ותמצית כדי שיהיה קל ככל האפשר להבין למה אתה מתכוון.

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

• מה הדפדפן שלך?

• מה הוצג על המסך כאשר נחסמה (מסך ריק? חלק ממשק המשחק? הודעת שגיאה?)

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

• מה הדפדפן שלך?

• איזה חלק של הכללים לא היה מכובד על ידי עיבוד 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

• האם אפשר לראות את הפרת החוק בשידור החוזר? אם כן, באיזה מספר מהלך?

• מה הדפדפן שלך?

• מה היה המהלך במשחק שרצית לבצע?

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

• מה ניסית לעשות שגרם לפעולה הזו

• מה קרה כאשר את/ה מנסה לעשות את זה (הודעת שגיאה, הודעת פס סטטוס משחק, ...)?

• מה הדפדפן שלך?

• באיזה שלב במשחק הבעייה קרתה (מה היו ההוראות הנכונות)

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

• מה קרה כאשר את/ה מנסה לבצע פעולת משחק (הודעת שגיאה, הודעת פס סטטוס משחק, ...)?

• מה הדפדפן שלך?

• אנא תאר/י את הנושא המוצג. 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

• מה הדפדפן שלך?

• בבקשה העתק והדבק את הטקסט המוצג באנגלית במקום בשפה שלך. 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. האם טקסט זה זמין במערכת התרגום? אם כן, האם היא תורגמה במשך יותר מ -24 שעות?

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

• מה הדפדפן שלך?

• אנא הסבר את ההצעה שלך במדויק ותמצית כדי שיהיה קל ככל האפשר להבין למה אתה מתכוון.

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

• מה הדפדפן שלך?