From 6f5abf933b62558423a91f999d9aaa261f6847ad Mon Sep 17 00:00:00 2001 From: David Beguin Date: Wed, 28 Aug 2019 14:06:50 +0000 Subject: [IMP] website,livechat : apply various imp and fix on visitor views Applies various improvements: - Remove welcome message if chat request usecase. - If a visitor is online: line is green / if offline: line is red (in the list view) - Visitors list view: add first / last connection fields and remove time_since_last_action - Avoid useless leave notification if the livechat channel is empty Fix - ACLS on website_visitor_page model (for im_livechat_group_user) - ACLS on website_visitor and website_visitor_page model (for sales_team.group_sale_salesman) - Update visitor lang if visitor change the website lang. - Create visitor twice when translated website (due to rerouting) - Avatar for visitor banner in discuss. (image_64 instead of old image_small) Task ID: 2056080 PR #36290 --- addons/website_livechat/static/src/xml/thread.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'addons/website_livechat/static/src/xml/thread.xml') diff --git a/addons/website_livechat/static/src/xml/thread.xml b/addons/website_livechat/static/src/xml/thread.xml index a8872290b2a..b257f5264b3 100644 --- a/addons/website_livechat/static/src/xml/thread.xml +++ b/addons/website_livechat/static/src/xml/thread.xml @@ -32,7 +32,7 @@
-- cgit v1.2.3 From b6288e54461426d7aac6cfc549cee3e90309a093 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9bastien=20Theys?= Date: Thu, 19 Sep 2019 10:23:39 +0000 Subject: [IMP] *: remove image_64 and clean views MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit There are too many image sizes. Since they are stored resized this takes time to generate when saving a new image, it's more rows on the attachment table, more files on the disk, ... 64px is close enough to 128px that it can be removed without a big impact on download size. It will even reduce download and number of requests when both images are displayed because now only one has to be downloaded and then benefit from cache. The difference between the two is typically around 1.5kB which is negligible these days, especially when the request overhead is around 0.5kB already, not even taking into account other factors such as latency. If a 64px image must absolutely be returned, it is still possible to pass the size parameters to the image route. But the current guideline is to handle resizing in the views when necessary. Views ===== - remove width and height attributes when existing CSS rules are overriding them (eg. `.oe_kanban_avatar` in the right context) - add CSS rules instead of width and height attributes when possible - use `object-fit: cover;` where width and height are forced to avoid distortion of non-square images - for products, use `object-fit: contain;` instead, keep ratio but without crop - add new CSS rules where the expected size was max 64px*64px before due to the image size itself - remove `img-fluid` where using size classes to avoid conflicting rules task-2060865 closes odoo/odoo#36147 Signed-off-by: Sébastien Theys (seb) --- addons/website_livechat/static/src/xml/thread.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'addons/website_livechat/static/src/xml/thread.xml') diff --git a/addons/website_livechat/static/src/xml/thread.xml b/addons/website_livechat/static/src/xml/thread.xml index b257f5264b3..aaab8703a52 100644 --- a/addons/website_livechat/static/src/xml/thread.xml +++ b/addons/website_livechat/static/src/xml/thread.xml @@ -32,7 +32,7 @@
-- cgit v1.2.3