new edx experience: process to change the codecast iframes

[remisharrock]

• Open the Excel sheet with all the codecast studio URL links and open your assigned link in your browser. It should open the unit containing the codecast in the edx studio. If you have problems, read the next point.

• Sometimes, even if you are already connected to edX with your account on another tab in your browser, when you click the link directly from the Excel file it redirects to an URL containing "https://authn.edx.org/login?next=XXXXXXXX" with XXXXXXX the encoded URL, then it agains redirects you almost instantly to your edx dashboard (https://courses.edx.org/dashboard) and you won't see the unit in the studio. Instead copy the link and paste it in the address bar of your browser, you shouldn't have any reditection. (Edx magic, part 1).

• Make sure you have the "preview" and "view live version" buttons on the top right; if not click the little arrow and on the title of the codecast to make the buttons appear (Edx magic, part 2) !

• scroll the timeline and watch for modifications in the height of the codecast.

• Find the maximum height (multiple heights are possible, find the max one) and note the timing (for example here it's around 3:00). To do that look at the right scrollbar to get a sense of the height.

• edit and make the following 3 changes: 1/ "height: 100vh;" to "height: 1100px;" 2/ change scrolling:yes to scrolling="no" (not shown in the GIF bellow) 3/ change width="100%" to width="95%" (not shown in the GIF bellow) then click OK and Save

• stay in "Draft (Unpublished changes)" before publishing to preview and make sure you don't have any scrollbar anymore in the "legacy experience". To do that go throught the timeline and make sure no scrollbar is appearing.

• Do not try to click "view in the new experience" because it will show you the old version and not the modified one (Edx magic, part 3). Indeed, it is impossible to preview the modifications in the new experience from a DRAFT state. You must PUBLISH and make the modifications LIVE in order to preview with the new experience, which is a little bit weird (Edx magic, part 4). Also, do not try to go click the "legacy experience" button to go back to the legacy version from the new experience because it will show the old version and not the modified one (Edx magic, part 5), as shown here:

• PUBLISH LIVE to be able to preview with the new experience and click the preview button and then the view in the new experience:

• Verify that you do not have any scrollbar while scrolling the timeline of the codecast, report any bug with a new issue that identifies the faulty codecast

[EllaHa]

To keep track of where we are, please fill in the the spreedsheet, with updates https://docs.google.com/spreadsheets/d/1g9BjTF3aFaYvaGEaYd7VeBC8IYqOZD8kTg5tvDk2kdY/edit?usp=sharing

[rserranosmith]

I think that in the instructions we are supposed to change scrolling="yes" to scrolling-"no", and not the other way around. Am I right? Also, for hiding the overflow, is the correct syntax overflow:hidden or overflow="hidden"?

[remisharrock]

Thanks @rserranosmith my mistake, I modified it. For overflow, I think it's even style="overflow: hidden" I have to double check...

[remisharrock]

looking at https://stackoverflow.com/questions/10082155/remove-scrollbar-from-iframe I don't really understand the correct way of using overflow hidden... anybody any idea ?

[remisharrock]

I finally decided to remove the overflow:hidden parameter and updated the process accordingly...

[rserranosmith]

There was a small issue with the width of the code cast being too large, and cutting off a portion of the timeline. To fix this, we found that reducing the width from 100% to 95% seemed to fix the issue. Below is a summary of the changes to be made, as well as a picture for reference

scrolling="no"
height: 1100px;
width="95%"

[remisharrock]

there are faulty ones after the modification and I'm opening new issues for them : https://github.com/remisharrock/c-programming-with-linux-MOOC-issues-tracker/issues/702 [update]: for me it's working, anbody can try again ?