First, the problem background:
On ios system, from App RESEARCH, gray environment, to enter the front page, adapted to enter the inlet from different models page, normally page display part, the display part of the page exception, a page code logic adapted models are merely request Interface, after acquiring the data to render it for loop
1, vue page code is as follows:
2, js code is as follows (data request, to fetch buffer with a buffer, the interface does not request to return fetch data, the direct assignment):
3, the interface returns the data as follows:
4, iOS addition, since the inquiry App, an inlet gradation environment, each of the other end, including iOS, from App RESEARCH, most inlet gradation environment (page into Vehicles) Normal follows:
5, ios, since research app, an inlet gradation environment (page into the model adaptation) following exception (page dom but has been rendered partially blank display; console where no error; request returns data interface portion has been shown; for example, the right letter; page does not block level elements, blank scrollable content, click the trigger to jump page; triggering a blank page after the jump, then jump back to the previous two pages, and can not fit into the entrance and then click models page):
Second, the Solution: originally suspected to be a side effect with keep-alive, the result is not a reason for exclusion, guess is more data-level, direct assignment influential? Plus with the traversal push no effect. Gradation guess whether network problems caused by binding reactive system, after the data request, the data assignment processing operations in this. After performing $ nextTick, found reproducing Probability decreased, only occasional, so he add timers, each end of each final test were normal environment.