If DOM input is prohibited, there will

[naive creek]

Yes, this is something to consider and will not prohibit dom input directly

[verbal drift]

Are you a team player?

[digital spade]

Hiii @verbal drift thanks for your feedback! We understand that enabling CSS + HTML fully will boost the creations to a better level, but we also need to take care of the overall security issue which is more important in this stage.
In the mean time, we’re working on the structure of the render system. And definitely we’d like to hear from you more about what kind of features you’d like to implement, which will greatly help us to progress!

[verbal drift]

Actually, I have a lot of ideas.

1. First of all, using HTML+CSS can solve many layout problems and make our visual effects better.
2. If some animation attributes of CSS can be supported, it will make the page more dynamic, such as zooming in and out of a certain word.
3. I originally wanted to make a bot for answering page countdown questions, but then I found that it did not support the timer in JS. Later, I learned that the output page can only be displayed once, and it does not support webapi, so it cannot be carried out.
   Yes, security issues are very important, and it is best if it can be controlled within a controllable range.

[verbal drift]

It suddenly occurred to me that if I could add some special effects to the page based on the conditions when the page jumps, for example, when I type "congratulations" and the page jumps to another page, a celebratory firework will pop up on the chat interface, which feels very cool.

[verbal drift]

I also thought of a function that can record the page time of the current state, so that I can count the completion time and give users a more intuitive data presentation. I can make many types of bots, such as bots that answer questions within a time limit, bots that display the time to pass a level, bots that divide levels according to time, etc.

[lofty fulcrum]

gm

gm