In our project, we use the vue-draggable-plus library, which utilizes the drag-and-drop functionality based on the browser drag-and-drop HTML5 API.
During dragging using the browser drag & drop (HTML5 DnD), the element has a drag preview style (that's what chat gpt says). By default, the browser automatically creates a transparent copy of the dragged element.
Is there any way to not display the transparent copy of the dragged element at all or shift it along the Y-axis so that it is not visible.
I'm specifically interested in the impact on the class of the browser HTML5 drag-and-drop!
Budget: 500 UAH Deadline: 1 day
Hello, Yaroslav
if you are interested specifically in how to disable browser drag-and-drop - write, I will help.
but it seems that with this bug, it's not so simple.
Hello, I need your help in implementing a task. Fix the bugs on the website page, the page displays a 404 error.
It is necessary to connect the application form on the landing page to keycrm. I will provide all necessary access. Please write how much time and cost this task will take.
There is a website on WordPress (Elementor + WooCommerce). Currently, there are issues with SEO and page indexing. The developer reports that due to Elementor, performance metrics are limited, but the main task now is correct indexing and SEO settings. What needs to be checked and fixed: 1. Page indexing Check which pages are closed from indexing Ensure that important pages (categories, products, service pages) are open for indexing Check for the presence of noindex / nofollow (in meta tags and through SEO plugins) Check WooCommerce page settings (products, categories, attributes) 2. Schema / microdata Check the current schema markup on the site Ensure that the Product schema is correctly connected for WooCommerce products Eliminate duplicates or incorrect schemas (if there are conflicts between Elementor + SEO plugin) 3. WordPress SEO settings Check settings in Yoast / RankMath (if used) Configure: robots.txt sitemap.xml canonical URLs Ensure that pages are not excluded from the sitemap 4. Technical check Check: indexing status through Google Search Console possible crawl errors redirects (301/302) Ensure that there are no critical blocks for Googlebot 5. Elementor / performance (as part of the SEO audit) Provide recommendations for reducing "junk" from Elementor (if it affects SEO) Check for content duplicates due to Elementor templates Work results The site is correctly indexed by Google Pages are open for search engines Sitemap and robots.txt are configured correctly There are no critical SEO errors in WooCommerce A brief report: what was found and fixed
Website for evaluation: https://copy.eurobrands-shop.de/ Task: fix frontend bugs at the Magento 2 / Amasty theme level: CSS/LESS/JS, mobile, RTL, minicart, language dropdown, layout shift/CLS. Work format: - without local Magento deployment; - work through DevTools + theme source files; - edits in CSS/LESS/JS/template files of the theme; - result: diff / commit / archive of changed files; - deployment and assembly on our side; - work through a secure deal; - NDA until the transfer of source files/accesses. What needs to be checked and evaluated: 1. RTL / Arabic version: - phone in the header is displayed incorrectly; - element offsets in header, minicart, wishlist/account, product page; - margins, direction, unicode-bidi, positioning. 2. Header: - language dropdown; - cart/wishlist; - hit-area of icons. 3. Minicart: - opens unstably on some pages; - check Console / Network / Event Listeners / customer-data / z-index / overlay. 4. Mobile: - cart/wishlist badges are too large; - Categories block is compressed/cut off; - mobile menu / Menu-Account. 5. Product page: - layout shift / CLS of images; - Add to Cart / Quantity / BOX / PALLET in RTL. 6. Wishlist/account: - /wishlist/ - /mwishlist/ - tabs, Back button, overflow of counters. Problematic URLs: - https://copy.eurobrands-shop.de/alpro - https://copy.eurobrands-shop.de/producers - https://copy.eurobrands-shop.de/wishlist/ - https://copy.eurobrands-shop.de/mwishlist/ In your response, please write: 1. Do you have experience with Magento 2 frontend? 2. Do you have experience with RTL? 3. How many hours do you need for the first stage? 4. What is the cost? 5. When can you start? 6. What accesses do you need? 7. Are you ready to work through a secure deal and sign an NDA? Important: a specific result is needed — corrections or a technical explanation for each point: fixed / not reproducible / not a frontend issue.
Improvement of the website's CR conversion. Tasks according to the specifications https://docs.google.com/document/d/1Y7zipbe2IEnFpthYuheAr6QA_50aR2Fz8V14rp5NpNo/edit?usp=sharingBOOK NOW buttonphoto / videoshort textAND IMMEDIATELY the booking formfixed (sticky)to repeat every 1–2 blocksof the same color (contrasting: red / green)