Editing Issues

Editing Performance (Lag)

If you experience lag or sluggishness while editing, please try refreshing the page.

If the issue persists, please send an email to our support team with the following details:

• Recipient: support@mockitt.com
• Subject: Editing Lag
• Email Content:
  1. Your browser version and operating system version.
  2. Are you using a VPN or network proxy?
  3. Does the lag occur in all files or only in specific files?
  4. If it is a specific file, please provide the file share link.

Unable to Save Files

If you are unable to save your file during editing, please follow these steps:

1. Do not close the editor tab. Open the browser's Developer Tools (Console) to check for errors.
   • Shortcut: Ctrl + Alt + I (Windows) or Cmd + Option + I (Mac).
2. Check the Console and Network tabs for any red error messages. If found, scroll to the bottom and take a screenshot.
3. Send an email to our support team so we can investigate the issue.

• Recipient: support@mockitt.com
• Subject: Unable to Save File
• Email Content:
  1. A description and screenshot of the save failure.
  2. A screenshot of the error messages in the Console.

Image Upload Failed

If you are unable to upload images, please report the issue to our support team.

• Recipient: support@mockitt.com
• Subject: Image Upload Failed
• Email Content:
  1. A screenshot showing the upload failure.
  2. The image file you were trying to upload (for testing purposes).

White Screen While Editing

If the editor turns white (blank screen) while you are working, it may be caused by a data anomaly within a specific component. Please contact us for assistance.

• Recipient: support@mockitt.com
• Subject: White Screen While Editing
• Email Content:
  1. Your Mockitt account email.
  2. The file share link.
  3. The name of the page, widget, or Component you were editing before the screen went white.
  4. A screenshot of the last few components you worked on (if possible).

Component Limit Reached

If you receive a warning that the number of components has exceeded 50,000 and you cannot add more, it means the file has reached the browser's loading limit. Adding more elements may prevent the file from opening.

Our team is continuously working to optimize the element loading limit. In the meantime, you can reduce the number of elements using the following methods:

1. Reduce Page States: If you need to create interactions within a page, use Dynamic Components instead of duplicating the entire page for each state. For example, if a page has 100 elements and you create 10 page states, the total element count becomes 1,000 (100x10).
2. Use Dynamic Components for Popups: Instead of copying a page and adding a mask/popup (which doubles the element count), use Dynamic Components:
   • Create a Dynamic Component containing the popup and mask. Set "State 1" as hidden and "State 2" as visible.
   • Drag it into the canvas.
   • Set a "Mouse Click" interaction on your trigger button to switch the Dynamic Component to "State 2".
3. Use Screenshots: For content that does not require interaction (such as complex charts or large tables with many elements), temporarily use a screenshot to represent them. You can replace the screenshot with actual components later when you need to edit that specific section or once loading limits are increased.